Repository navigation
[Crossgen2 CI] Composite_LargeVersionBubble: widespread test failures on linux x64 and windows x64 #16
Description
Failure Details
- Pipeline: runtime-coreclr crossgen2-composite
- Build: 1354390 (also 1353280)
- Jobs:
Composite_LargeVersionBubble linux x64 checked,Composite_LargeVersionBubble windows x64 checked - Configuration: linux x64, windows x64 / checked
- Error Category: test-failure
Scope of Failure
Multiple Helix work items fail in the Composite_LargeVersionBubble configuration:
linux x64 Composite_LargeVersionBubble (job eb043f17):
- CoreMangLib
- Directed_1
- Directed_2
- Directed_3
- Exceptions
- GC
- GC-features
- GC-scenarios1
- IL_Conformance
windows x64 Composite_LargeVersionBubble (job cc55f0cc):
- CoreMangLib
- (additional work items may be truncated)
Error Output
Error details
Helix console logs are not accessible without authentication.
Representative Helix references:
https://helix.dot.net/api/2019-06-17/jobs/eb043f17-b572-4327-93d6-de4eb9137934/workitems/CoreMangLib/consolehttps://helix.dot.net/api/2019-06-17/jobs/eb043f17-b572-4327-93d6-de4eb9137934/workitems/GC/consolehttps://helix.dot.net/api/2019-06-17/jobs/eb043f17-b572-4327-93d6-de4eb9137934/workitems/Exceptions/console
Recurring Pattern
This failure pattern has been observed in at least 2 consecutive crossgen2-composite builds on main (1353280 and 1354390), confirming it is a persistent regression.
Analysis
The Composite_LargeVersionBubble mode compiles all assemblies together in a single composite R2R image with a large version bubble. The breadth of failing work items (CoreMangLib, Directed, Exceptions, GC, GC-features, GC-scenarios, IL_Conformance) on linux x64 and windows x64 suggests a codegen issue specific to composite large-version-bubble compilation.
Recommended Action
This failure requires deeper investigation:
- Check recent changes to composite compilation in crossgen2 (
src/coreclr/tools/aot/crossgen2/) - The Large Version Bubble mode enables cross-module inlining — the regression may be in how cross-module references are handled
- Examine Helix logs for specific test-level failures
- Compare failing tests against their non-LVB composite counterparts to isolate LVB-specific regressions
Note
🔒 Integrity filter blocked 5 items
The following items were blocked because they don't meet the GitHub integrity level.
- #114359
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #113285
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #111865
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #107364
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #110173
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools:
github:
min-integrity: approved # merged | approved | unapproved | noneGenerated by Crossgen2 CI Failure Triage · ◷
- expires on Apr 26, 2026, 2:12 PM UTC
Activity
arm64: Fold negative variable eq/ne to 0 (dotnet#124332)
jtschuster commentedon Mar 31, 2026
CI Failure Analysis — Grouped Issues Filed
Deep investigation of builds 1354390 and 1353280 identified 5 distinct failure modes. Each has been filed as a separate issue:
Summary
The Interop failures (#21) and LVB R2RDump failures (#22) together account for the vast majority of failures seen in these builds.
Note
This analysis was performed by Copilot.
Scan method body for dependencies (#16)
github-actions commentedon Apr 17, 2026
Recurrence
The LVB failure scope has stabilized at JIT.performance and Regression_3 work items on both linux x64 and windows x64. This is consistent with the R2RDump crash pattern tracked in
#22.Use acquire reads for cast cache entries (dotnet#132630)