Test failure: JIT/Methodical/explicit/basic/refloc_i4_r/refloc_i4_r.cmd

[v-wenyuxu]

Failed in: runtime-coreclr gcstress-extra 20250215.1

Failed tests:

coreclr windows arm64 Checked gcstress0xc_disabler2r_jitstress2 @ Windows.11.Arm64.Open
    - JIT/Methodical/explicit/basic/refloc_i4_r/refloc_i4_r.cmd

Error message:

 
cmdLine:C:hwAF790966wB37B09E2eJITMethodicalMethodical_r1../explicit/basic/refloc_i4_r/refloc_i4_r.cmd Timed Out (timeout in milliseconds: 5400000 from variable __TestTimeout, start: 2/15/2025 11:04:00 PM, end: 2/16/2025 12:34:01 AM)

Return code:      -100
Raw output file:      C:hwAF790966wB37B09E2uploadsexplicit�asic
efloc_i4_routput.txt
Raw output:
BEGIN EXECUTION
 "C:hwAF790966pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  refloc_i4_r.dll 
finalizer called.
*** passed ***

cmdLine:C:hwAF790966wB37B09E2eJITMethodicalMethodical_r1../explicit/basic/refloc_i4_r/refloc_i4_r.cmd Timed Out (timeout in milliseconds: 5400000 from variable __TestTimeout, start: 2/15/2025 11:04:00 PM, end: 2/16/2025 12:34:01 AM)
Unable to find cdb.exe at C:Program Files (x86)Windows Kits10Debuggers�rm64cdb.exe
Test Harness Exitcode is : -100
To run the test:
Set up CORE_ROOT and run.
> C:hwAF790966wB37B09E2eJITMethodicalMethodical_r1../explicit/basic/refloc_i4_r/refloc_i4_r.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__TestExecutor273|0_274(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]

Looks like yet another timeout on win-arm64 when running JitStress, similar to #112546 and #112332. These timeouts started roughly around the time we started running Cobalt machines in CI; @kunalspathak do you still have access to your Cobalt VM? Since we aren't seeing similar failures on osx-arm64, I think this might be specific to Cobalt, and I'm hoping we can try to repro it by running CoreCLR tests with JitStress enabled on one of the test machines.

I suppose this could be a manifestation of #105780, though the 3-opt infinite loop issue I recently fixed has made me wary of the JIT doing questionable things under JitStress.

cc @dotnet/jit-contrib

[JulieLeeMSFT]

Assinging to @kunalspathak.

[kunalspathak]

I will close this because we didn't see it lately and seems there is a generic timeout issue for which I have added some logging in #112724. If we see similar issue lets open a new one with updated logging to better diagnose it.