CI failures on main: `@azure/openai` (Build) and `@azure/arm-computelimit` (Analyze)

[github-actions]

Summary

Two CI pipeline failures detected on the main branch as of commit e69fec317 (2026-05-06). The check-run results were reported against the HEAD commit but the builds were triggered by earlier commits—most notably #38391 ("Add imports field to all warp-built packages"), which modified package.json for both affected packages, and #38429 ("Sync eng/common directory with azure-sdk-tools for PR 15504"), which updated common/tools/eslint-plugin-azure-sdk/ and pipeline templates.

---

Failures

@azure/openai

Check run: js - openai (Build Build) (Build ID [6257332]((dev.azure.com/redacted)

Failing step: Build Build (npm build / pnpm pack pipeline step)

Error annotations from CI:

Bash exited with code '2'.
Manifest generation failed, please check output file for more info.
Path does not exist: /mnt/vss/_work/_temp/packages-dev-publish
Script failed with exit code: 1

Root cause analysis:

PR #38391 added an imports field to sdk/openai/openai/package.json:

"imports": {
  "#platform/*": {
    "react-native": "./src/*-react-native.mts",
    "browser": "./src/*-browser.mts",
    "default": "./src/*.ts"
  }
}

The @azure/openai package (sdk/openai/openai) has browser and react-native warp build targets. The warp build tool (common/tools/warp) processes the imports field at build time: it resolves #platform/* specifiers in emitted files and validates resolved targets exist on disk.

However, sdk/openai/openai/src/ contains no .mts files (*-react-native.mts, *-browser.mts). The warp build's resolveImports post-processing step iterates over the imports map and, for entries that are referenced in source code, checks that the resolved target files exist. The build then fails with "Manifest generation failed" (likely the CI wrapper's phrasing for a non-zero exit from the warp build / npm run build), and since no .tgz artifact is produced, the subsequent packages-dev-publish staging step fails with "Path does not exist".

The openai source currently has an empty src/index.ts (documentation comment only) and the real exports live under src/types/. No source file uses #platform/* imports, but the warp validation of the wildcard pattern referencing non-existent files may still cause a build failure.

Suggested fix:

Either (a) remove the imports field from sdk/openai/openai/package.json since it was added generically and the package doesn't yet use platform-specific imports, or (b) create stub files for the missing .mts targets:

--- a/sdk/openai/openai/package.json
+++ b/sdk/openai/openai/package.json
@@ -... @@
-  "imports": {
-    "#platform/*": {
-      "react-native": "./src/*-react-native.mts",
-      "browser": "./src/*-browser.mts",
-      "default": "./src/*.ts"
-    }
-  },

Reproduced locally: No — pnpm is not available in this environment. The full warp build error can be seen in the [Azure DevOps build log]((dev.azure.com/redacted)

---

@azure/arm-computelimit

Check run: js - computelimit - mgmt (Build Analyze) (Build ID [6257415]((dev.azure.com/redacted)

Failing step: Build Analyze (PowerShell step in the analyze pipeline)

Error annotations from CI:

PowerShell exited with code '1'.

Root cause analysis:

Two recent changes potentially affect this package:

1. PR #38391 added an imports field to sdk/computelimit/arm-computelimit/package.json:

   "imports": {
     "#platform/*": {
       "default": "./src/*.ts"
     }
   }

   Some PowerShell pipeline scripts read package.json and may not handle the "#platform/*" key (containing # and * special characters) gracefully when parsing or filtering JSON.

2. PR #38429 (eng/common sync) added new source files to common/tools/eslint-plugin-azure-sdk/, including a new src/configs/index.ts that is now imported by src/index.ts. If the analyze step rebuilds the eslint plugin (needed to pick up the new ts-package-json-required-scripts rule now enabled as "error" in azure-sdk-customized.ts), a build failure in the plugin would cascade to any package running pnpm lint.

The analyze pipeline for management packages (archetype-sdk-client.yml) includes spell-checking, README verification, and package validation steps—any of these PowerShell steps could have exited with code 1.

Suggested fix:

Access the full [Azure DevOps build log]((dev.azure.com/redacted) to identify which specific PowerShell step failed. If the failure is caused by the imports field breaking a script, either sanitize the field before processing or remove/strip the imports field from management SDK packages (since they are Node-only and don't benefit from platform-specific imports today).

Reproduced locally: No — pnpm is not available in this environment.

---

Additional Notes

• Both failures are new on the current HEAD commit; neither appeared on the previous commits checked (98bbc31c, 3de1abed for different packages).
• No known pre-existing failures apply (per issue #37864).
• The Build Build failure for @azure/openai is a build-step failure (not a unit-test failure); the failing tests themselves may be green, but without a successful build the test stage never runs.
• Full CI logs are in Azure DevOps and are required to confirm the exact failing command for the computelimit analyze step.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• centralus2.in.applicationinsights.azure.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "centralus2.in.applicationinsights.azure.com"

See Network Configuration for more information.

Generated by Analyze CI Test Failures · ● 6.6M · ◷

[deyaaeldeen]

Incorrect analysis