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.

Sign up for GitHub

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

Jump to bottom

System.Net.Security.Tests timing out #64943

Closed
runfoapp bot opened this issue Feb 7, 2022 · 6 comments · Fixed by #64966
Closed

System.Net.Security.Tests timing out #64943

runfoapp bot opened this issue Feb 7, 2022 · 6 comments · Fixed by #64966
Labels
area-System.Net os-windows
Milestone
6.0.x

Comments

@runfoapp
Copy link

runfoapp bot commented Feb 7, 2022 •
edited
Loading 

   System.Net.Security.Tests: [Long Running Test] 'System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_MismatchProtocols_Fails', Elapsed: 00:04:04
   System.Net.Security.Tests: [Long Running Test] 'System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_MismatchProtocols_Fails', Elapsed: 00:06:04
['System.Net.Security.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

Runfo Tracking Issue: System.Net.Security.Tests timing out

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1598876 runtime-extra-platforms PR 60905 net7.0-windows-Release-x86-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1598876 runtime-extra-platforms PR 60905 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1598596 runtime-extra-platforms PR 63546 net7.0-windows-Release-x86-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1598596 runtime-extra-platforms PR 63546 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1598024 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1598024 runtime-extra-platforms PR 64830 net7.0-windows-Release-x86-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1597924 runtime-extra-platforms PR 64330 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1597902 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1597254 runtime-extra-platforms PR 64806 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596968 runtime-extra-platforms PR 64330 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596825 runtime-extra-platforms PR 64567 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596825 runtime-extra-platforms PR 64567 net7.0-OSX-Release-x64-CoreCLR_release-OSX.1200.Amd64.Open console.log
1596647 runtime-extra-platforms PR 64897 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596337 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1595857 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1595438 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594956 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594944 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594386 runtime-extra-platforms PR 62740 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594252 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1593948 runtime-extra-platforms PR 64806 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1593924 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1593924 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
2 18 18
@dotnet-issue-labeler dotnet-issue-labeler bot added area-System.Net untriaged New issue has not been triaged by the area owner labels Feb 7, 2022
@ghost
Copy link

ghost commented Feb 7, 2022

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

Issue Details

Runfo Creating Tracking Issue (data being generated)

Author: runfoapp[bot]
Assignees: -
Labels:

area-System.Net, untriaged
Milestone: -

@elinor-fung
Copy link
Member

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 -----

@wfurt
Copy link
Member

wfurt commented Feb 7, 2022

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

@elinor-fung elinor-fung mentioned this issue Feb 7, 2022
Closed
@wfurt wfurt mentioned this issue Feb 8, 2022
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Feb 8, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Feb 9, 2022
@elinor-fung
Copy link
Member

@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()

@elinor-fung
Copy link
Member

Filed the actual test failures as a separate issue so that runfo will track it: #65098

@ghost ghost locked as resolved and limited conversation to collaborators Mar 12, 2022
@karelz karelz modified the milestones: 7.0.0, 6.0.x Apr 8, 2022
@karelz
Copy link
Member

karelz commented Apr 8, 2022

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

@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Apr 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-System.Net os-windows
Projects
None yet
Milestone
6.0.x
Development

Successfully merging a pull request may close this issue.

improve SslStream tests on misconfigured systems wfurt/runtime
3 participants
@karelz @wfurt @elinor-fung