-
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
TLS1.3 networking tests are flaky on Windows 11 #58927
Comments
Tagging subscribers to this area: @dotnet/ncl, @vcsjones Issue DetailsConfiguration:
Also note the time this took: 250s.
|
I looked at your issue but the assembly is different and I didn't see any mention of Tsl1.3 which is why I opened a new one :) |
BTW this feels like real product issue. (.NET or Windows) |
Based on the runfo data (see above) this test is failing quite a lot. @wfurt would you mind disabling the tests for now on W11? |
Triage: We should disable the tests now. @wfurt has Schannel traces to share with OS team. |
Tests were disabled in PR #59135 in main (7.0) |
|
SslStream_NegotiateClientCertificateAsyncTls13_Succeeds was part of the change @vcsjones. Interestingly I could not find any failures in Kusto database. Maybe @karelz will have more luck or it is sign that something is not right. |
Hit in #63032. |
sure. We generally don't touch the release brunch unless there is specific reason. I assume test only changes can go in without ship room, right? I'll get PRs up. |
Yes, just tag me and @danmoseley and either of us can merge. |
If we have a test-only change to help pass rates, it's always worth porting it. It will pay off as we're using this branch for the next 3 years. |
I'mm not arguing agains. But our visibility to 6.0 runs is very limited at the moment. |
Ah - you're concerned about causing other breaks? I trust your team's judgement of course. |
no. but in general we don't pay attention to release branches AFAIK. |
should be fixed by May non-sec update (5C) or June security update (6B) Windows update. |
doesn't seem like flaky, it consistently fails on this configuration. Relevant log in case full log disappears (
|
This is different failure than the original |
Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1353292&view=ms.vss-test-web.build-test-results-tab&runId=39586706&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=167012
Configuration:
net7.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open
Also note the time this took: 250s.
cc @dotnet/ncl @karelz @am11
Runfo Tracking Issue: system.net.security.tests.apmsslstreamsystemdefaulttest.clientandserver_oneorbothusedefault_ok
Displaying 100 of 272 results
Build Result Summary
The text was updated successfully, but these errors were encountered: