Skip to content

[ci-scan] Test failure: GC/Regressions/Github/Runtime_129681 Crossgen2 exit 255 on osx x64 R2R #132037

Description

@github-actions

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1545184
Build error leg or test failing: coreclr Pri1 Runtime Tests Run R2R_CG2 osx x64 checked — GC/Regressions/Github/Runtime_129681/Runtime_129681

Pipeline: runtime-coreclr outerloop (definition 108), branch main. The failure reproduces on the R2R_CG2 osx x64 checked leg and persists into follow-up build 1545348.

Error Details

The GC/Regressions/Github/Runtime_129681 test compiles its assembly with Crossgen2 (R2R composite, --method-layout:random, --verify-type-and-field-layout) before running. On the osx x64 leg targeting osx/x64, Crossgen2 aborts with exit code 255, so the test harness records a non-zero exit and the test fails.

Running test: GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
Running CrossGen2:  crossgen2 @...Runtime_129681.dll.rsp
Crossgen2 failed with exitcode: 255
Test Harness Exitcode is : 1
END EXECUTION - FAILED

Error Message

{
  "ErrorMessage": [
    "Running test: GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd",
    "Crossgen2 failed with exitcode: 255"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

First build it occurred

The signature is present in source build 1545184 (2026-08-08), the prior build 1544819 (2026-08-07), and follow-up build 1545348 (2026-08-08) — at least three consecutive occurrences.

Duplicate search

Searched open and closed issues/KBEs for Runtime_129681 and Crossgen2 failed with exitcode: 255 on the osx x64 R2R leg: no existing KBE matches. Merged PR #131947 ("Fix AV in gc_heap::init_heap_segment", merged 2026-08-07) is unrelated to this Crossgen2 codegen failure and merged before the follow-up build that still reproduces the 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

Build Repository Test Pull Request
1545742 dotnet/runtime GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
1545710 dotnet/runtime GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
1545681 dotnet/runtime GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
1545624 dotnet/runtime GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
1545609 dotnet/runtime GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd
1545482 dotnet/runtime GC/Regressions/Github/Runtime_129681/Runtime_129681/Runtime_129681.cmd

Summary

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Build ErrorUse this to report build issues in the .NET Helix tabagentic-workflowsarea-GC-coreclrblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'untriagedNew issue has not been triaged by the area owner

    Type

    No type

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions