Repository navigation
[ci-scan] Build break: SuperPMI asmdiffs browser-wasm — no MCH collection available #132053
Copy link
Copy link
Closed
Closed
Copy link
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabagentic-workflowsarch-wasmWebAssembly architectureWebAssembly architecturearea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Milestone
Description
Activity
- addedblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tab
on Aug 9, 2026 - addeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Aug 9, 2026 - addedarch-wasmWebAssembly architectureWebAssembly architecturearea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
on Aug 10, 2026 dotnet-policy-service commented
on Aug 10, 2026 ContributorMore actionsTagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.dotnet-policy-service commented
on Aug 10, 2026 ContributorMore actionsTagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.This was caused by overly broad helix test monitor enablement. As a result the merge step did not wait for the helix step to finish, and so found no files to merge. Should be fixed by #132084
- removeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Aug 10, 2026 And indeed was fixed.
- locked and limited conversation to collaborators
on Sep 11, 2026
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabagentic-workflowsarch-wasmWebAssembly architectureWebAssembly architecturearea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1545358
Build error leg or test failing: SuperPMI asmdiffs checked release windows x64 — browser-wasm work item
Pipeline:
runtime-coreclr superpmi-asmdiffs-checked-release(definition 153), branchmain. Thebrowser-wasmSuperPMI asmdiffs work item fails because no MCH (method context) collection files are available in Azure Storage for the browser/wasm (x64) target under the current JIT-EE version GUID305cdd16-2cee-49af-ae7c-2537eb37cae9. The download step finds nothing to fetch, so asmdiffs has no collections to run and the work item exits with code 1. The failure persists into follow-up build 1545748.Error Details
Error Message
{ "ErrorMessage": [ "asmdiffs --diff_with_release --no_progress -core_root", "No MCH files found to replay" ], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }First build it occurred
Source build 1545358 (2026-08-08); the immediately preceding completed build 1536356 (2026-08-02) succeeded. The signature reproduces in follow-up build 1545748 (2026-08-09).
Duplicate search
Searched open/closed issues and open PRs for
superpmi asmdiffs browser wasm MCHandNo MCH files found to replay: no existing KBE matches the browser-wasm asmdiffs target. The osx-arm64 superpmi-replay manifestation of the same "no MCH collection available" root cause is tracked separately in #132036 (different pipeline, target, and signature), which does not cover the browser-wasm asmdiffs leg.Filed by
ci-failure-scan(detection only).ci-failure-fixwalks open[ci-scan]KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Report
Summary