Repository navigation
Test Failure: tracing/eventpipe/rundownvalidation/rundownvalidation/rundownvalidation.cmd #133280
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578663
Build error leg or test failing: tracing/eventpipe/rundownvalidation/rundownvalidation/rundownvalidation.cmd
3.5s: liveStubBlocks: 1
3.5s: rundownStubBlocks: 1
3.5s: rundownWriteBarriers: 1
3.5s: ==TEST FINISHED: PASSED!==
7.2s: LCG jump-stub loads: 1
7.2s: LCG jump-stub unloads: 0
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
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorPattern": ".+LCG jump-stub unloads: 0",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578663
Error message validated: [.+LCG jump-stub unloads: 0]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/4/2026 11:49:57 PM UTC
Report
| Build | Repository | Test | Pull Request |
|---|---|---|---|
| 1588980 | dotnet/runtime | tracing/eventpipe/rundownvalidation/rundownvalidation/rundownvalidation.cmd | |
| 1585871 | dotnet/runtime | tracing/eventpipe/rundownvalidation/rundownvalidation/rundownvalidation.cmd | |
| 1578663 | dotnet/runtime | tracing/eventpipe/rundownvalidation/rundownvalidation/rundownvalidation.cmd |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 2 | 3 |
Activity
lateralusX commentedon Sep 10, 2026
@brianrob, looks like #132190 introduced this failure since this validation also runs for the coreclr interpreter test leg, and looks like it validates artifacts specific to JIT codegen. Maybe that check should be excluded on coreclr interpreter? I assigned the issue over to you, if you can't address it, please let me know.
brianrob commentedon Sep 11, 2026
Thanks for sending this my way @lateralusX. I have a PR to address this.
Skip LCG Jump-Stub Validation In Rundown Validation Test Under Interp…