[ci-scan] Test failure: JIT/opt/GuardedDevirtualization/badinlinee returns 101 on composite-R2R windows-arm64 gcstress

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1604094
Build error leg or test failing: coreclr Pri1 Runtime Tests Run Composite windows arm64 checked @ windows.11.arm64.open - JIT.opt.0.1 (JIT/opt/GuardedDevirtualization/badinlinee)

Pipeline: runtime-coreclr crossgen2-composite gcstress (definition 141), branch main. The JIT/opt/GuardedDevirtualization/badinlinee test fails on the composite R2R windows arm64 checked leg under gcstress: the test returns 101 instead of the expected 100 (and the harness records a wrapped -1), so the R2R composite run of badinlinee.dll fails. The failure reproduces on source build 1604094 (2026-09-20) and persists into follow-up build 1604685 (2026-09-21, two legs).

KBE authoring guidance (ci-failure-scan)

Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
Build Analysis parses only the single JSON block under Error Message.
ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.

Error Details

"...\corerun.exe" ... badinlinee.dll
Test allocated 84992 bytes
Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 100
Actual:   -1
   at __GeneratedMainWrapper.Main()
Expected: 100
Actual: 101
END EXECUTION - FAILED
Failed test: JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd

Error Message

{
  "ErrorMessage": [
    "Test allocated 84992 bytes",
    "Failed test: JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log

First build it occurred

This composite-gcstress badinlinee failure appears in source build 1604094 (2026-09-20) and follow-up build 1604685 (2026-09-21). Definition 141 runs on a weekend/weekly cadence and has failed continuously across the scanned window; the true origin of this specific test failure may predate 2026-09-20.

Duplicate search

Searched open and closed Known Build Error issues, area trackers, and open PRs for badinlinee, GuardedDevirtualization, and the composite-R2R gcstress leg: no existing KBE, tracker, or fix PR matches this test failure.

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.

Generated by CI Outer-Loop Failure Scanner · opus48 · 997.2 AIC · ⌖ 15 AIC · ⊞ 19.2K · ◷

Report

Build	Repository	Test
1614304	dotnet/runtime	JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd
1613975	dotnet/runtime	JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd
1613538	dotnet/runtime	JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd
1613360	dotnet/runtime	JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd

Summary

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

Failed in: runtime-coreclr pgostress 20260925.1

Failed tests:

coreclr linux x64 Checked instrument_if_optimizing @ AzureLinux.3.Amd64.Open
- JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd
coreclr linux arm Checked instrument_if_optimizing @ (Debian.13.Arm32.Open)[email protected]/dotnet-buildtools/prereqs:debian-13-helix-arm32v7@sha256:38844e127f1c1422bfbbfcb56012dfefc906d728f6a305bfd1aae70881ac6941
- JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd
coreclr linux arm64 Checked instrument_if_optimizing @ AzureLinux.3.Arm64.Open
- JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd
coreclr osx arm64 Checked instrument_if_optimizing @ OSX.26.Arm64.Open
- JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd

Error message:


Return code:      1
Raw output file:      /datadisks/disk1/work/AD13095B/w/AE92093F/uploads/GuardedDevirtualization/badinlinee/output.txt
Raw output:
BEGIN EXECUTION
/datadisks/disk1/work/AD13095B/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true badinlinee.dll ''
Test allocated 24000 bytes
Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 100
Actual:   -1
   at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/EqualityAsserts.cs:line 102
   at Xunit.Assert.Equal[T](T expected, T actual) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/EqualityAsserts.cs:line 36
   at __GeneratedMainWrapper.Main()
Expected: 100
Actual: 101
END EXECUTION - FAILED
Test Harness Exitcode is : 1
To run the test:
Set up CORE_ROOT and run.
> /datadisks/disk1/work/AD13095B/w/AE92093F/e/JIT/opt/JIT.opt/../GuardedDevirtualization/badinlinee/badinlinee.sh

Stack trace:

   at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 135
   at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix) in /__w/1/s/src/tests/Common/CoreCLRTestLibrary/OutOfProcessTest.cs:line 202
   at Program.<>c__DisplayClass0_0.<<Main>$>g__TestExecutor475|476(StreamWriter tempLogSw, StreamWriter statsCsvSw, StreamWriter outOfProcessPlanWriter)

@JulieLeeMSFT

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Workflow artifact: ci-fix
Artifact kind: handoff
Linked KBE: #134694

Note

AI/Copilot-generated triage note.

This Known Build Error has no producible automated code change (reason: JIT/GC codegen — must not be auto-fixed), so I could not open even a best-effort PR. Looping in owners so it can be fixed forward rather than muted.

Root cause (best analysis)

The composite R2R Windows ARM64 gcstress leg runs JIT/opt/GuardedDevirtualization/badinlinee and returns 101 instead of 100 (reported by the harness as -1). This is a codegen-stress failure; changing the test or calling pattern would be an out-of-bounds workaround rather than a fix.

Evidence

Failing build: 1604094
First build it occurred: 1604094 — 2026-09-20 UTC (computed within the scanned window; may not be the true origin)
Possible related PR: none identified with sufficient confidence
The latest completed definition-141 build, 1614304, failed on 2026-09-28 UTC, confirming the gcstress leg remains live.

Suggested reviewers / area contacts

Area owners (area-CodeGen-coreclr): @dotnet/jit-contrib

A JIT owner should reproduce under the composite R2R gcstress configuration and correct the generated behavior behind the changed test result.

Structured data:

{
  "artifact_kind": "handoff",
  "linked_kbe": 134694,
  "workflow_artifact": "ci-fix"
}

Generated by CI Outer-Loop Failure Fixer · gpt56 · 63.2 AIC · ⌖ 11.5 AIC · ⊞ 26.9K · ◷

Fix missing env.vars in JIT tests (dotnet#134703)

Navigation Menu

Repository navigation

[ci-scan] Test failure: JIT/opt/GuardedDevirtualization/badinlinee returns 101 on composite-R2R windows-arm64 gcstress #134694

Build Information

Error Details

Error Message

First build it occurred

Duplicate search

Report

Summary

Root cause (best analysis)

Evidence

Suggested reviewers / area contacts

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[ci-scan] Test failure: JIT/opt/GuardedDevirtualization/badinlinee returns 101 on composite-R2R windows-arm64 gcstress #134694

Description

Build Information

Error Details

Error Message

First build it occurred

Duplicate search

Report

Summary

Activity

VincentBu commented on Sep 28, 2026

dotnet-policy-service commented on Sep 28, 2026

github-actions commented on Sep 29, 2026

Root cause (best analysis)

Evidence

Suggested reviewers / area contacts

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions