Test failure: System.Net.Quic.Tests.MsQuicTests.OpenStreamAsync_BlocksUntilAvailable_PeerClosesWritingUnidirectional

[VincentBu]

Failed in: runtime-coreclr libraries-jitstress 20260124.1

Failed tests:

net11.0-windows-Release-x64-jitstress1_tiered-Windows.10.Amd64.Open
- System.Net.Quic.Tests.MsQuicTests.OpenStreamAsync_BlocksUntilAvailable_PeerClosesWritingUnidirectional
net11.0-windows-Release-x64-jitstress2_tiered-Windows.10.Amd64.Open
- System.Net.Quic.Tests.MsQuicTests.OpenStreamAsync_BlocksUntilAvailable_PeerClosesWritingUnidirectional

Error message:

System.InvalidOperationException : Operation is not valid due to the current state of the object.

Stack trace:

   at System.Net.Quic.ResettableValueTaskSource.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/Internal/ResettableValueTaskSource.cs:line 251
   at System.Runtime.CompilerServices.AsyncHelpers.RuntimeAsyncTask`1.DispatchContinuations() in /_/src/coreclr/System.Private.CoreLib/src/System/Runtime/CompilerServices/AsyncHelpers.CoreCLR.cs:line 459
--- End of stack trace from previous location ---
   at System.Net.Quic.Tests.MsQuicTests.OpenStreamAsync_BlocksUntilAvailable_PeerClosesWritingUnidirectional() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicTests.cs:line 806
--- End of stack trace from previous location ---
   at System.Net.Quic.Tests.MsQuicTests.OpenStreamAsync_BlocksUntilAvailable_PeerClosesWritingUnidirectional() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicTests.cs:line 813
   at System.Runtime.CompilerServices.AsyncHelpers.RuntimeAsyncTask`1.DispatchContinuations() in /_/src/coreclr/System.Private.CoreLib/src/System/Runtime/CompilerServices/AsyncHelpers.CoreCLR.cs:line 459
--- End of stack trace from previous location ---
--- End of stack trace from previous location ---

[dotnet-policy-service]

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[ManickaP]

Based on Kusto, this happened once, on a single run, on JitStress where the app was overloaded and started rejecting incoming connections. I'm gonna close this as a fluke as it is highly unlikely we could anything about it at this stage.