System.Net.Security.Tests timing out #64943

Activity

1. ghost added

   area-System.Net

   on Feb 7, 2022
2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Feb 7, 2022
4. elinor-fung commented on Feb 7, 2022

   

   elinor-fung

   on Feb 7, 2022

   Member

   More actions

   Seems to only be on Server2022 - likely related to / the same as #64941. A bunch of the tests are failing with similar errors:

    System.Net.Security.Tests.ServerNoEncryptionTest.ServerNoEncryption_ClientNoEncryption_ConnectWithNoEncryption [FAIL]
         System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
         ---- System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.
         Stack Trace:
           /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs(352,0): at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
           /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerNoEncryptionTest.cs(88,0): at System.Net.Security.Tests.ServerNoEncryptionTest.ServerNoEncryption_ClientNoEncryption_ConnectWithNoEncryption()
           --- End of stack trace from previous location ---
           ----- Inner Stack Trace -----
   
5. wfurt

   added

   os-windows

   on Feb 7, 2022
6. wfurt commented on Feb 7, 2022

   

   wfurt

   on Feb 7, 2022

   Member

   More actions

   Yes, we should use this opportunity to fix the tests to fail instead of hanging.
7. ghost added

   in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

   on Feb 8, 2022
8. wfurt

   closed this as completedin #64966on Feb 9, 2022
9. ghost removed

   in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

   on Feb 9, 2022
10. elinor-fung commented on Feb 9, 2022

    

    elinor-fung

    on Feb 9, 2022

    Member

    More actions

    @wfurt The System.Net.Security tests are no longer timing out, but a number of them are failing in the latest rolling build (which has #64966).

    Log: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-faadee89bd794674a4/System.Net.Security.Tests/3/console.5430d545.log?%3Fsv%3D2019-07-07%26se%3D2022-03-01T10%253A03%253A37Z%26sr%3Dc%26sp%3Drl%26sig%3D7KaC%252FNNbfcddwp5hSAXuN8viAbBFoDJX%252B7goKB5UlE4%253D

    It looks like a mix of still trying to use a protocol that is not available:

    System.Net.Security.Tests.ServerNoEncryptionTest.ServerNoEncryption_ClientAllowNoEncryption_ConnectWithNoEncryption [FAIL]
        System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
        ---- System.ComponentModel.Win32Exception : The function requested is not supported
        Stack Trace:
        /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs(403,0): at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerNoEncryptionTest.cs(62,0): at System.Net.Security.Tests.ServerNoEncryptionTest.ServerNoEncryption_ClientAllowNoEncryption_ConnectWithNoEncryption()
        --- End of stack trace from previous location ---
        ----- Inner Stack Trace -----
        
    System.Net.Security.Tests.ServerNoEncryptionTest.ServerNoEncryption_ClientNoEncryption_ConnectWithNoEncryption [FAIL]
        System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
        ---- System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.
        Stack Trace:
        /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs(349,0): at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerNoEncryptionTest.cs(88,0): at System.Net.Security.Tests.ServerNoEncryptionTest.ServerNoEncryption_ClientNoEncryption_ConnectWithNoEncryption()
    

    Getting a different exception type (because of the missing availability?):

    System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_MismatchProtocols_Fails(serverProtocol: Tls12, clientProtocol: Tls11, expectedException: typeof(System.Security.Authentication.AuthenticationException)) [FAIL]
        Assert.IsAssignableFrom() Failure
        Expected: typeof(System.Security.Authentication.AuthenticationException)
        Actual:   typeof(System.IO.IOException)
        Stack Trace:
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs(64,0): at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_MismatchProtocols_Fails(SslProtocols serverProtocol, SslProtocols clientProtocol, Type expectedException)
        --- End of stack trace from previous location ---
        Output:
        Server: Tls11; Client: Tls12
    System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_MismatchProtocols_Fails(serverProtocol: Tls11, clientProtocol: Tls12, expectedException: typeof(System.Security.Authentication.AuthenticationException)) [FAIL]
        Assert.IsAssignableFrom() Failure
        Expected: typeof(System.Security.Authentication.AuthenticationException)
        Actual:   typeof(System.ComponentModel.Win32Exception)
        Stack Trace:
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs(64,0): at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_MismatchProtocols_Fails(SslProtocols serverProtocol, SslProtocols clientProtocol, Type expectedException)
        --- End of stack trace from previous location ---
    System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_MismatchProtocols_Fails(serverProtocol: Tls, clientProtocol: Tls12, expectedException: typeof(System.Security.Authentication.AuthenticationException)) [FAIL]
        Assert.IsAssignableFrom() Failure
        Expected: typeof(System.Security.Authentication.AuthenticationException)
        Actual:   typeof(System.TimeoutException)
        Stack Trace:
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerAsyncAuthenticateTest.cs(63,0): at System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_MismatchProtocols_Fails(SslProtocols serverProtocol, SslProtocols clientProtocol, Type expectedException)
    

    And the xunit exception for skipping a test being thrown and not caught during remote execution:

    System.Net.Security.Tests.LoggingTest.EventSource_EventsRaisedAsExpected [FAIL]
        Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception.
        Stack Trace:
        
        Child exception:
            Microsoft.DotNet.XUnitExtensions.SkipTestException: Unstable on Windows 11
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/SslStreamStreamToStreamTest.cs(79,0): at System.Net.Security.Tests.SslStreamStreamToStreamTest.SslStream_StreamToStream_Authentication_Success(X509Certificate serverCert, X509Certificate clientCert)
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/LoggingTest.cs(45,0): at System.Net.Security.Tests.LoggingTest.<>c.<EventSource_EventsRaisedAsExpected>b__1_1()
        /_/src/libraries/Common/tests/System/Diagnostics/Tracing/TestEventListener.cs(111,0): at System.Diagnostics.Tracing.TestEventListener.RunWithCallback(Action`1 handler, Action body)
        /_/src/libraries/System.Net.Security/tests/FunctionalTests/LoggingTest.cs(41,0): at System.Net.Security.Tests.LoggingTest.<>c.<EventSource_EventsRaisedAsExpected>b__1_0()
        
        Child process:
            System.Net.Security.Tests, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 System.Net.Security.Tests.LoggingTest+<>c Void <EventSource_EventsRaisedAsExpected>b__1_0()
    
11. elinor-fung commented on Feb 9, 2022

    

    elinor-fung

    on Feb 9, 2022

    Member

    More actions

    Filed the actual test failures as a separate issue so that runfo will track it: #65098
12. ghost locked as resolved and limited conversation to collaborators on Mar 12, 2022
13. karelz

    modified the milestones: 7.0.0, 6.0.x on Apr 8, 2022
14. karelz commented on Apr 8, 2022

    

    karelz

    on Apr 8, 2022

    Member

    More actions

    Fixed in 7.0 (main) in PR #64966 and in 6.0.4 in PR #65024.
15. karelz

    removed

    untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

    on Apr 8, 2022