Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test failure: System.Net.Quic.Tests.QuicStreamTests.TestStreams #107969

Open
v-wenyuxu opened this issue Sep 18, 2024 · 1 comment
Open

Test failure: System.Net.Quic.Tests.QuicStreamTests.TestStreams #107969

v-wenyuxu opened this issue Sep 18, 2024 · 1 comment
Labels
arch-arm32 area-System.Net.Quic blocking-clean-ci-optional Blocking optional rolling runs JitStress CLR JIT issues involving JIT internal stress modes os-linux Linux OS (any supported distro) untriaged New issue has not been triaged by the area owner

Comments

@v-wenyuxu
Copy link

Failed in: runtime-coreclr libraries-jitstress 20240917.1

Failed tests:

net9.0-linux-Release-arm-no_tiered_compilation-(Debian.12.Arm32.Open)[email protected]/dotnet-buildtools/prereqs:debian-12-helix-arm32v7
    - System.Net.Quic.Tests.QuicStreamTests.TestStreams
    - System.Net.Quic.Tests.QuicStreamTests.GetStreamIdWithoutStartWorks
    - System.Net.Quic.Tests.QuicStreamTests.ReadOutstanding_ReadAborted_Throws
    - System.Net.Quic.Tests.QuicStreamTests.MultipleReadsAndWrites
    - System.Net.Quic.Tests.QuicStreamTests.WaitForReadsClosedAsync_ConnectionClosed_Throws
    - System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ConnectionClosed_Throws
    - System.Net.Quic.Tests.QuicStreamTests.MultipleConcurrentStreamsOnSingleConnection
    - System.Net.Quic.Tests.QuicStreamTests.AbortAfterDispose_StreamCreationFlushedByDispose_Success
    - System.Net.Quic.Tests.QuicStreamTests.BasicTest
    - System.Net.Quic.Tests.QuicStreamTests.Read_SynchronousCompletion_Success
    - System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ServerShutdown_Success
    - System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ServerWriteAborted_Throws
    - System.Net.Quic.Tests.QuicStreamTests.LargeDataSentAndReceived
    - System.Net.Quic.Tests.QuicStreamTests.WaitForReadsClosedAsync_ServerReadAborted_Throws
    - System.Net.Quic.Tests.QuicStreamTests.WriteAsync_LocalAbort_Throws
    - System.Net.Quic.Tests.QuicStreamTests.WriteAbortedWithoutWriting_ReadThrows
    - System.Net.Quic.Tests.QuicStreamTests.WriteCanceled_NextWriteThrows
    - System.Net.Quic.Tests.QuicStreamTests.ReadAbortedWithoutReading_WriteThrows
    - System.Net.Quic.Tests.QuicStreamTests.WaitForWritesClosedAsync_ClientReadAborted_Throws
    - System.Net.Quic.Tests.QuicStreamTests.WaitForWriteCompletionAsync_ClientReadAborted_Throws
    - System.Net.Quic.Tests.QuicStreamTests.WritePreCanceled_Throws
    - System.Net.Quic.Tests.QuicStreamTests.WaitForReadsClosedAsync_GracefulShutdown_Success
    - System.Net.Quic.Tests.QuicStreamTests.WaitForReadsClosedAsync_ClientWriteAborted_Throws
    - System.Net.Quic.Tests.QuicStreamTests.MultipleStreamsOnSingleConnection

Error message:

 System.Net.Quic.QuicException : The connection timed out from inactivity.

Stack trace:

   at System.Net.Quic.QuicConnection.HandleEventShutdownInitiatedByTransport(_SHUTDOWN_INITIATED_BY_TRANSPORT_e__Struct& data) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 659
   at System.Net.Quic.QuicConnection.HandleConnectionEvent(QUIC_CONNECTION_EVENT& connectionEvent) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 761
   at System.Net.Quic.QuicConnection.NativeCallback(QUIC_HANDLE* connection, Void* context, QUIC_CONNECTION_EVENT* connectionEvent) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 796
--- End of stack trace from previous ___location ---
   at System.Net.Quic.QuicConnection.OpenOutboundStreamAsync(QuicStreamType type, CancellationToken cancellationToken) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 553
   at System.Net.Quic.Tests.QuicStreamTests.CreateAndTestBidirectionalStream(QuicConnection c1, QuicConnection c2) in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs:line 286
   at System.Net.Quic.Tests.QuicStreamTests.TestStreams() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs:line 276
   at System.Net.Quic.Tests.QuicStreamTests.TestStreams() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs:line 280
   at System.Net.Quic.Tests.QuicStreamTests.TestStreams() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs:line 280
   at System.Net.Quic.Tests.QuicStreamTests.TestStreams() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs:line 280
--- End of stack trace from previous ___location ---
@v-wenyuxu v-wenyuxu added arch-arm32 os-linux Linux OS (any supported distro) JitStress CLR JIT issues involving JIT internal stress modes blocking-clean-ci-optional Blocking optional rolling runs labels Sep 18, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Sep 18, 2024
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-arm32 area-System.Net.Quic blocking-clean-ci-optional Blocking optional rolling runs JitStress CLR JIT issues involving JIT internal stress modes os-linux Linux OS (any supported distro) untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

1 participant