-
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.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_SslProtocols_Test #64941
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
It seems like the Helix machine has Tls 1.0 and 1.1 explicitly disabled. #64923 will be definitely needed. Makes me wonder why #64919 did not see it. does not seems to have any 2022 entries unless I missed something. Related to https://github.com/dotnet/core-eng/issues/15394 cc: @MattGal |
Well that's odd. While it is indeed related to https://github.com/dotnet/core-eng/issues/15394, I've received exception to not make any changes to test machines and none have been made. It may be a "secure-by-default" thing on newer Windows SKUs... if you can provide the correlation id of a run with problems or even better the Queue id that's always helpful to start with. Reaching out on Teams to get more info. |
This is Fromm machine running helix-repro subscription. |
Unfortunately since I'm not you I can't tell what image you're using. If you're asking us to change this it does represent a change from previous but I'll also need to know what image(s) you think should be this way. |
I believe is because I didn't run the extra-platforms-pipeline 🤦 |
Some of the tests in the most recent rolling build - which has #64923 - are still failing the same way. Maybe there is some more environment detection that needs to be handled? |
Or maybe some tests need to be updated to use the platform detection checks? For example
|
I did not see HTTP failures in the posted link. |
but looking at the test: yes, it should check if given versions are supported instead assuming it. |
Apparently the failures didn't show in the summary/timeline (no idea why). But the tests tab shows failures in HTTP, Security, and Quic - direct link to one of the failing test results: https://dev.azure.com/dnceng/public/_build/results?buildId=1599183&view=ms.vss-test-web.build-test-results-tab&runId=44675088&resultId=189644 |
SocketsHttpHandler_HttpClientHandler_SslProtocols_Test
are all failing. Example failure:Runfo Tracking Issue: System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_SslProtocols_Test
Displaying 100 of 212 results
Build Result Summary
The text was updated successfully, but these errors were encountered: