Enable disabled QUIC tests (#56590)

With update updated MsQuic on Linux in place (PR #56429) we should pass few more disabled tests. I did ~200 local runs and I did not see any problems Fixes #55242 Fixes #55746
dotnet · Jul 30, 2021 · 38071bf · 38071bf
1 parent fae1412
commit 38071bf
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 5 deletions.
diff --git a/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicConnectionTests.cs b/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicConnectionTests.cs
@@ -50,7 +50,6 @@ private static async Task<QuicStream> OpenAndUseStreamAsync(QuicConnection c)
         }
 
         [Fact]
-        [ActiveIssue("https://github.com/dotnet/runtime/issues/55242", TestPlatforms.Linux)]
         public async Task CloseAsync_WithPendingAcceptAndConnect_PendingAndSubsequentThrowOperationAbortedException()
         {
             using var sync = new SemaphoreSlim(0);
@@ -96,7 +95,6 @@ await RunClientServer(
         }
 
         [Fact]
-        [ActiveIssue("https://github.com/dotnet/runtime/issues/55242", TestPlatforms.Linux)]
         public async Task Dispose_WithPendingAcceptAndConnect_PendingAndSubsequentThrowOperationAbortedException()
         {
             using var sync = new SemaphoreSlim(0);
@@ -130,7 +128,6 @@ await RunClientServer(
         }
 
         [Fact]
-        [ActiveIssue("https://github.com/dotnet/runtime/issues/55242", TestPlatforms.Linux)]
         public async Task ConnectionClosedByPeer_WithPendingAcceptAndConnect_PendingAndSubsequentThrowConnectionAbortedException()
         {
             if (IsMockProvider)

diff --git a/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs b/src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs
@@ -573,8 +573,7 @@ await RunClientServer(
                     await using QuicStream stream = await connection.AcceptStreamAsync();
 
                     QuicStreamAbortedException ex = await Assert.ThrowsAsync<QuicStreamAbortedException>(() => WriteForever(stream));
-                    // [ActiveIssue("https://github.com/dotnet/runtime/issues/55746")]
-                    //Assert.Equal(expectedErrorCode, ex.ErrorCode);
+                    Assert.Equal(expectedErrorCode, ex.ErrorCode);
 
                     // We should still return true from CanWrite, even though the write has been aborted.
                     Assert.True(stream.CanWrite);