-
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
Connect_DualMode_DnsConnect_RetrievedEndPoints_Success - SocketException: Transport endpoint is not connected #55709
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsRunfo Tracking Issue: Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure
Build Result Summary
|
I think this is more a networking issue, the test is failing with:
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRunfo Tracking Issue: Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure
Build Result Summary
|
@tmds any further thoughts here and on the related issue which didn't disappear? |
Test disabled on Linux in PR #56003 on 7/20 |
Note, the sibling test Connect_DualMode_MultiAddressFamilyConnect_RetrievedEndPoints_Success has now 2 new failures as well, after fix to #55053 ... we may have to disable it as well ... Failures 5/27-7/30 (incl. PRs) for Connect_DualMode_MultiAddressFamilyConnect_RetrievedEndPoints_Success test:
cc @antonfirsov |
Runfo Tracking Issue: Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure
Build Result Summary
Failure
Failures 5/20-7/19 (incl. PRs):
The text was updated successfully, but these errors were encountered: