[NOREVIEW][NOMERGE] HTTP/3 stress data corruption hunt #101624
Closed
Build Analysis / Build Analysis
failed
Jul 16, 2024 in 0s
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Known test errors
-
❌System.Net.Quic.Tests.MsQuicTests.Read_ReadsCompleted_ReportedBeforeReturning0 - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.MsQuicTests.Read_ReadsCompleted_ReportedBeforeReturning0 - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.MsQuicTests.QuicRootedObjectGetReleased - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicConnectionTests.Dispose_WithoutClose_ConnectionClosesWithDefault - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicConnectionTests.CloseAsync_PendingOpenStream_Throws - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicConnectionTests.CloseAsync_WithOpenStream_LocalAndPeerStreamsFailWithQuicOperationAbortedException - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_GracefulShutdown_Success - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_GracefulShutdown_Success - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.QuicStreamTests.Read_WriteAborted_Throws - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.Read_WriteAborted_Throws - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.QuicStreamTests.ReadsClosedFinishes_ConnectionClose - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.ReadsWritesClosedFinish_StreamDisposed - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.Read_SynchronousCompletion_Success - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ServerShutdown_Success - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ServerShutdown_Success - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ServerWriteAborted_Throws - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ServerWriteAborted_Throws - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.QuicStreamTests.LargeDataSentAndReceived - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.LargeDataSentAndReceived - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.QuicStreamTests.WritesClosedFinishes_ConnectionClose - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForReadsClosedAsync_ClientCompleteWrites_Success - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WriteAsync_LocalAbort_Throws - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ClientReadAborted_Throws - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ClientReadAborted_Throws - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWriteCompletionAsync_ClientReadAborted_Throws - CI error: System.Net.Quic.QuicException: The connection timed out from inactivity
-
❌System.Net.Quic.Tests.QuicStreamTests.WaitForWriteCompletionAsync_ClientReadAborted_Throws - [6.0, 7.0, 8.0] Connection reset assert failure in System.Net.Sockets.Tests.SendReceive_SyncForceNonBlocking.TcpReceiveSendGetsCanceledByDispose
Test Failures (17 tests failed)
🔹 [All failing tests from runtime]
- Ubuntu.2204.Arm64.Open
- Debian.11.Arm64.Open
- net9.0-osx-Debug-x64-Mono_Minijit_Debug-OSX.1200.Amd64.Open
- net9.0-osx-Debug-x64-coreclr_release-OSX.1200.Amd64.Open
- net9.0-osx-Debug-x64-coreclr_checked-OSX.1200.Amd64.Open
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net9.0-linux-Debug-x64-Mono_Minijit_Debug-Ubuntu.2204.Amd64.Open
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net9.0-linux-Debug-x64-Mono_Interpreter_Debug-Ubuntu.2204.Amd64.Open
- net9.0-windows-Debug-x64-coreclr_release-Windows.Amd64.Server2022.Open
- net9.0-windows-Debug-x64-coreclr_release-Windows.11.Amd64.Client.Open
- Alpine.316.Amd64.Open
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net9.0-linux-Debug-x64-coreclr_release-Ubuntu.2204.Amd64.Open
❌ System.Net.Quic.Functional.Tests.WorkItemExecution [Console] [Details] [Artifacts] [2.35% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configurations (17)
Loading