You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipeline: runtime-coreclr outerloop (definition 108), branch main. The failure reproduces on both osx.15.amd64 machines behind the plain osx x64 checked leg (jobs e2334af3 / 1132d4aa) in source build 1545348 and persists into follow-up build 1545482 (job 31e71870).
This is a distinct failure mode from the Crossgen2 exit-255 signature tracked by #132037 on the R2R_CG2 osx x64 leg: here the plain (non-R2R) osx x64 leg runs the same test but the runtime host aborts during startup with coreclr_initialize failed - Error: 0x80004005. The Crossgen2 failed with exitcode: 255 line from #132037 does not appear in this log.
Error Details
Running test: GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
External disassembler is not available.
BEGIN: coreclr_initialize failed - Error: 0x80004005
END: coreclr_initialize failed - Error: 0x80004005
Return code: 1
...
Expected: 100
Actual: 255
END EXECUTION - FAILED
Test Harness Exitcode is : 1
Observed in source build 1545348 (2026-08-08) on both osx x64 machines and again in follow-up build 1545482 (2026-08-08) — at least two distinct builds.
Duplicate search
Searched open and closed issues/KBEs for Runtime_129681, coreclr_initialize failed, and 0x80004005: the only existing test-specific KBE is #132037, which matches a different signature (Crossgen2 failed with exitcode: 255) on the R2R_CG2 leg and does not match this plain-leg startup failure. Related: #132037. No open or merged PR references 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 GitHub Copilot agentic workflow.
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:
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1545348
Build error leg or test failing: coreclr Pri1 Runtime Tests Run osx x64 checked — GC/Regressions/Github/Runtime_129681/Runtime_129681
Pipeline:
runtime-coreclr outerloop(definition 108), branchmain. The failure reproduces on both osx.15.amd64 machines behind the plainosx x64 checkedleg (jobse2334af3/1132d4aa) in source build 1545348 and persists into follow-up build 1545482 (job31e71870).This is a distinct failure mode from the Crossgen2 exit-255 signature tracked by #132037 on the R2R_CG2 osx x64 leg: here the plain (non-R2R) osx x64 leg runs the same test but the runtime host aborts during startup with
coreclr_initialize failed - Error: 0x80004005. TheCrossgen2 failed with exitcode: 255line from #132037 does not appear in this log.Error Details
Error Message
{ "ErrorMessage": [ "Running test: GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd", "BEGIN: coreclr_initialize failed - Error: 0x80004005" ], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }First build it occurred
Observed in source build 1545348 (2026-08-08) on both osx x64 machines and again in follow-up build 1545482 (2026-08-08) — at least two distinct builds.
Duplicate search
Searched open and closed issues/KBEs for
Runtime_129681,coreclr_initialize failed, and0x80004005: the only existing test-specific KBE is #132037, which matches a different signature (Crossgen2 failed with exitcode: 255) on the R2R_CG2 leg and does not match this plain-leg startup failure. Related: #132037. No open or merged PR references this signature.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.Note
This issue was generated by the
ci-failure-scanGitHub Copilot agentic workflow.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Report
Summary