[ci-scan] Test failure: superpmi-asmdiffs browser-wasm no MCH files to replay

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1441956
Build error leg or test failing: SuperPMI asmdiffs checked release windows x64 - browser-wasm

Error Details

The browser-wasm SuperPMI asmdiffs work item fails because no MCH (method context) collection files exist for the browser/x64/ target in Azure Storage. The collection pipeline either stopped producing MCH files for this target or the target was recently added without a corresponding collection.

No Azure Storage MCH files to download from 31a04b06-915e-42a0-bbd2-c9c397677ae5/browser/x64/
[11:30:38] Disk usage (C:\h\w\A702090E\p): total 126 GB; free 98 GB; consumed by download 0 GB
[11:30:38] No MCH files found to replay

Failure in C:\h\w\A702090E\w\AC370919\uploads\superpmi_browser_wasm.log

Affected pipeline:

• runtime-coreclr superpmi-asmdiffs-checked-release (def 153)

Related (closed, windows-arm64 variant): #127805

Error Message

{
  "ErrorMessage": "No MCH files found to replay",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

First build it occurred

• Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1441956
• Finished: 2026-05-30
• Occurrences: 2 consecutive builds (May 30, May 31)
• Prior build 1433376 on 2026-05-24 succeeded.

---

Filed by ci-failure-scan, which scans dnceng-public outer-loop pipelines on main and converts stable failures into KBEs.

Note

🔒 Integrity filter blocked 42 items

The following items were blocked because they don't meet the GitHub integrity level.

• #5158 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7096 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5984 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5101 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5318 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #44158 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5637 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7231 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5130 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #128959 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #67082 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #114222 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #128365 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #48070 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #88027 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #96968 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 26 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 93.5M · ◷

Report

Summary

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

[AndyAyersMS]

I think this is just a startup transient. Kicked off a new run here:

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1450418&view=results

[AndyAyersMS]

That failed (though it found the MCH). Two issues to sort out:

• The job is using a stale version of coredistools cached in our azure blob storage rather than the one restored via nuget
• The check/release mode discards of the embedded jit config settings, so turns of the NYI_WASM to R2R failure path.