-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Tests under: System.Net.Security.Tests.ServerAsyncAuthenticateTest failed with "System.ComponentModel.Win32Exception" #23692
Comments
@davidsh can network glitches cause this error or is it something different? |
I don't think it is a network glitch. These tests use loopback. The problem I think is due to X509 certificate bugs (caused by PFX files being used for certificates) and tests running in parallel. @bartonjs had previously commented on this in #23221 which had similar X509 issues. This still needs to be debugged further. |
BTW: Last failure was on 11/3 |
The failure BTW: There are other, likely unrelated failures in these tests later on - not tracked by this issue. Closing. Please reopen if it happens again. |
Failed tests:
System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_EachSupportedProtocol_Success
System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_MismatchProtocols_Fails
Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_netcoreapp_win7_release/272/testReport/System.Net.Security.Tests/ServerAsyncAuthenticateTest/ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success_serverProtocol__Tls_/
Configuration: outerloop_netcoreapp_win7_release
MESSAGE:
STACK TRACE:
The text was updated successfully, but these errors were encountered: