[ci-scan] Test failure: superpmi-replay osx-arm64 no MCH files available

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1544047
Build error leg or test failing: SuperPMI replay standard windows x64 checked — osx-arm64 work items (1 through 9)

Pipeline: runtime-coreclr superpmi-replay (definition 150), branch main. All 9 osx-arm64 SuperPMI replay work items fail, and the failure persists into follow-up build 1545320.

Error Details

SuperPMI replay for the osx-arm64 target fails because no MCH (method context) collection files are available in Azure Storage for the current JIT-EE version GUID 305cdd16-2cee-49af-ae7c-2537eb37cae9. The download step reports no files to fetch, so replay has nothing to run and each work item exits with code 1.

Running superpmi.py download
No Azure Storage MCH files to download from 305cdd16-2cee-49af-ae7c-2537eb37cae9/osx/arm64/
Running superpmi.py replay for JitStressRegs=0
No Azure Storage MCH files to download from 305cdd16-2cee-49af-ae7c-2537eb37cae9/osx/arm64/
No MCH files found to replay

This is the osx-arm64 target manifestation of the "no MCH collection available" failure; the windows-arm64 target variant was tracked separately in the now-closed #129427 / #129575 (different JIT-EE GUID and target path), which do not cover osx-arm64.

Error Message

{
  "ErrorMessage": [
    "download --no_progress -target_os osx -target_arch arm64",
    "No MCH files found to replay"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

First build it occurred

Earliest occurrence in the scanned window is source build 1544047 (2026-08-07); the immediately preceding build 1542173 (2026-08-06) succeeded. The signature reproduces in follow-up build 1545320 (2026-08-08).

Duplicate search

Searched open and closed Known Build Error issues for No MCH files found to replay, superpmi replay osx arm64, and the JIT-EE GUID: no open KBE matches. Closed windows-arm64 predecessors #129427 and #129575 cover a different target (windows/arm64) and JIT-EE GUID and are not this signature.

---

Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.

Note

This issue was generated by the ci-failure-scan Copilot (AI) automation workflow. Signatures and build references were verified against public AzDO / Helix logs.

Warning

Firewall blocked 1 domain

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

• awmgmcpg

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

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by CI Outer-Loop Failure Scanner · 489 AIC · ⌖ 16.4 AIC · ⊞ 18.3K · ◷

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0