Test failure: JIT/Regression/JitBlue/Runtime_71611/Runtime_71611/Runtime_71611.cmd

[v-wenyuxu]

Failed in: runtime-coreclr jitstress2-jitstressregs 20250209.1

Failed tests:

coreclr windows arm64 Checked jitstress2_jitstressregs4 @ Windows.11.Arm64.Open
    - JIT/Regression/JitBlue/Runtime_71611/Runtime_71611/Runtime_71611.cmd

Error message:

 
cmdLine:C:hwB56B09E5wBA970A30eJITRegressionRegression_2../JitBlue/Runtime_71611/Runtime_71611/Runtime_71611.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 2/9/2025 6:58:31 PM, end: 2/9/2025 7:28:31 PM)

Return code:      -100
Raw output file:      C:hwB56B09E5wBA970A30uploadsJitBlueRuntime_71611Runtime_71611output.txt
Raw output:
BEGIN EXECUTION
 "C:hwB56B09E5pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  Runtime_71611.dll 

cmdLine:C:hwB56B09E5wBA970A30eJITRegressionRegression_2../JitBlue/Runtime_71611/Runtime_71611/Runtime_71611.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 2/9/2025 6:58:31 PM, end: 2/9/2025 7:28:31 PM)
Test Harness Exitcode is : -100
To run the test:
Set up CORE_ROOT and run.
> C:hwB56B09E5wBA970A30eJITRegressionRegression_2../JitBlue/Runtime_71611/Runtime_71611/Runtime_71611.cmd

Stack trace:

   at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 141
   at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
   at Program.<<Main>$>g__TestExecutor584|0_585(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)

[dotnet-policy-service]

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

[amanasifkhalid]

The timestamps suggest this test hit a 30-minute runtime limit. I'm not able to repro any oddly long execution time locally on win-x64, but I think something is up here (it's not the 3-opt issue from last week).

cc @dotnet/jit-contrib.

set DOTNET_TieredCompilation=0
set DOTNET_JitStress=2
set DOTNET_JitStressRegs=4