Test failure: Regressions/coreclr/GitHub_16833/Test16833/Test16833.cmd

[v-wenyuxu]

Failed in: runtime-coreclr jitstress 20250212.1

Failed tests:

coreclr windows arm64 Checked jitstress1 @ Windows.11.Arm64.Open
    - Regressions/coreclr/GitHub_16833/Test16833/Test16833.cmd

Error message:

 
cmdLine:C:hwB4720988wB71C0982eRegressionsRegressions../coreclr/GitHub_16833/Test16833/Test16833.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 2/13/2025 5:41:08 AM, end: 2/13/2025 6:11:08 AM)

Return code:      -100
Raw output file:      C:hwB4720988wB71C0982uploadscoreclrGitHub_16833Test16833output.txt
Raw output:
BEGIN EXECUTION
 "C:hwB4720988pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  Test16833.dll 
Test SUCCEEDED

cmdLine:C:hwB4720988wB71C0982eRegressionsRegressions../coreclr/GitHub_16833/Test16833/Test16833.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 2/13/2025 5:41:08 AM, end: 2/13/2025 6:11:08 AM)
Test Harness Exitcode is : -100
To run the test:
Set up CORE_ROOT and run.
> C:hwB4720988wB71C0982eRegressionsRegressions../coreclr/GitHub_16833/Test16833/Test16833.cmd

Stack trace:

   at Xunit.Assert.True(Boolean condition, String userMessage) in /_/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 123
   at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
   at Program.<<Main>$>g__TestExecutor46|0_47(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]

I suspect this is the same issue as #112332. @dotnet/jit-contrib does anyone have a win-arm64 machine they can try reproducing the failure on? I'm unable to get an arm64 altjit stuck on this test.

[AndyAyersMS]

I can probably look this afternoon sometime

[kunalspathak]

I verified this and #112332 and was not able to repro this. I would recommend to keep an eye on this weekend run to see if this is intermittent infra failure.

[JulieLeeMSFT]

@kunalspathak, PTAL arm64 related timeouts.

[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.