[ci-scan] Outage suspected: widespread outer-loop failures across 22+ pipelines

[github-actions]

Reasoning

The CI scanner's outage circuit breaker tripped this run. Per-failure KBEs/PRs were NOT emitted; this issue is the single consolidated record so the failure set is not lost.

Trip totals:

• total-actionable-failures: 91
• pipelines-mostly-red: 4
• top-signature-share: 0.25 (NativeAOT build break CS7036: 23/91)

Breached threshold(s): total-actionable-failures > 30, pipelines-mostly-red >= 4

Impact on platforms

• runtime-nativeaot-outerloop (265): 23/23 legs failed — build break (CS7036 in CorInfoImpl.ReadyToRun.cs). Already tracked in [ci-scan] Build break: CS7036 in CorInfoImpl.ReadyToRun.cs after PR #126904 (runtime-nativeaot-outerloop) #128108 (closed).
• runtime-extra-platforms (154): 21/57 legs failed — mixed mobile/WASM/NativeAOT test failures.
• gc-standalone (146): 8/13 legs failed — GC standalone test failures on linux-arm64, windows-x64.
• runtime-libraries-interpreter (330): 2/2 legs failed (linux-x64, osx-arm64).
• runtime-coreclr libraries-jitstress-random (160): 3/6 legs failed.
• runtime-coreclr outerloop (108): 2 legs failed.
• runtime-coreclr crossgen2 (124): 2/19 legs failed.
• runtime-diagnostics (309): 2/16 legs failed.
• Additional failures across 15+ other stress/outer-loop pipelines.

Errors log

Top signature (NativeAOT build break, 23 occurrences):
src\coreclr\tools\aot\ILCompiler.ReadyToRun\JitInterface\CorInfoImpl.ReadyToRun.cs(2070,99): error CS7036: There is no argument given that corresponds to the required parameter 'strippedInstantiation' of 'CorInfoImpl.HandleToModuleToken(ref CORINFO_RESOLVED_TOKEN, out bool)'

Other affected pipelines have diverse test failure signatures requiring individual triage once totals normalize.

First build it occurred

• Earliest build in the scanned window with the dominant signature: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1417853
• Window size: 5 builds per pipeline (last 7 days)

Recommended action

• Human review needed before per-failure processing resumes.
• The NativeAOT build break ([ci-scan] Build break: CS7036 in CorInfoImpl.ReadyToRun.cs after PR #126904 (runtime-nativeaot-outerloop) #128108) is already tracked and closed — once a new pipeline run picks up the fix, 23 failures drop off and the totals may normalize.
• The next scheduled run re-evaluates from a fresh build sample. If the totals fall below the thresholds, per-failure KBEs/PRs resume automatically.
• A human can short-circuit by filing the root-cause KBE manually; once Build Analysis matches the dominant signature, per-leg counts fall and subsequent runs converge.
• Affected pipelines: 265, 154, 146, 330, 160, 108, 111, 113, 114, 115, 116, 118, 119, 124, 138, 140, 145, 155, 159, 235, 309, 316
• Top signatures: CS7036 HandleToModuleToken (23), various GC/stress/mobile test failures (68 combined)

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

[kotlarmilos]

Good attempt but not actionable, this makes sense when the CI is in more stable state