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
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 1 |
1 |
1 |
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), branchmain. TheJIT/opt/GuardedDevirtualization/badinlineetest fails on the composite R2R windows arm64 checked leg under gcstress: the test returns101instead of the expected100(and the harness records a wrapped-1), so the R2R composite run ofbadinlinee.dllfails. 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 Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.Error Message.ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.Error Details
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
badinlineefailure 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 Errorissues, area trackers, and open PRs forbadinlinee,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-fixwalks open[ci-scan]KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.Report
Summary