-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Net.Security.Tests ClientAsyncAuthenticate_MismatchProtocols_Fails on Server 2022 #65098
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
Triage: New queue which breaks our tests. |
Currently, all recent failures are when the server specifies the SSL3 protocol, the test also is not running very often (only jobs in the last 30 days, both failed with same parameters). #65120 changed the type of expected exception when one of the protocol is SSL3/2, so that may be the reason we started to see these failures, thoughts, @wfurt? |
AFAK we should not even try Ssl3 for Server2022. It feels like we should track it separately. The queue runs only when somebody explicitly asks. (unfortunately) |
@wfurt , do you think we should exempt SSL3 from testing or ask dceng disable SSL3 on servers in that particular queue? |
The linked issue fails with something using SslProtocolSupport.SupportedSslProtocolsTestData. We should figure out if SSL3 actually works on the given queue and if not we should improve protocol support detection. Aside from the protocol being enable/disabled explicitly we bump to issue with @antonfirsov where the handshake was failing because all weak cipher suites were disabled. (like TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA) As next steps, I think we should figure out if the failure is predictable - note that the Helix image is different than stock Server 2022 and https://github.com/dotnet/core-eng/issues/15528 should be done soon. |
Failed again in: runtime-coreclr libraries-jitstressregs 20220403.1 Failed test:
Error message:
|
CI db shows two (possibly distinct) types of failures:
I will disable the test for now. |
what is the exception for server 2022? |
For Server 2022, its |
The test failures stopped occuring on 04/15, when wfurt's fixes were merged (likely #68083), so we can consider this resolved. |
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:
Getting a different exception type (because of the missing availability?):
And the xunit exception for skipping a test being thrown and not caught during remote execution:
Runfo Tracking Issue: System.Net.Security.Tests ClientAsyncAuthenticate_MismatchProtocols_Fails on Server 2022
Displaying 100 of 1222 results
Build Result Summary
The text was updated successfully, but these errors were encountered: