Skip to content
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

Closed
runfoapp bot opened this issue Jul 15, 2021 · 8 comments · Fixed by #56399
Assignees
Labels
area-System.Net.Sockets disabled-test The test is disabled in source code against the issue os-linux Linux OS (any supported distro) test-run-core Test failures in .NET Core test runs
Milestone

Comments

@runfoapp
Copy link

runfoapp bot commented Jul 15, 2021

Runfo Tracking Issue: Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1237035 runtime Rolling net6.0-Linux-Release-arm64-CoreCLR_release-(Ubuntu.1804.ArmArch.Open)[email protected]/dotnet-buildtools/prereqs:ubuntu-16.04-helix-arm64v8-20210106155927-56c6673 console.log runclient.py
1234963 runtime Rolling net6.0-Linux-Release-x64-Mono_release-(Fedora.32.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:fedora-32-helix-20210710031120-870c408 console.log runclient.py
1232399 runtime PR 55499 net6.0-Linux-Debug-x64-Mono_release-SLES.15.Amd64.Open console.log runclient.py
1231144 runtime PR 55446 net6.0-Linux-Debug-x64-Mono_release-SLES.15.Amd64.Open console.log runclient.py
1230745 runtime Rolling net6.0-Linux-Release-x64-CoreCLR_release-SLES.15.Amd64.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 5 5

Failure

System.Net.Sockets.SocketException : Transport endpoint is not connected

   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) in /_/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs:line 3712
   at System.Net.Sockets.Socket.get_RemoteEndPoint() in /_/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs:line 355
   at System.Net.Sockets.Tests.Connect`1.Connect_DualMode_DnsConnect_RetrievedEndPoints_Success() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/Connect.cs:line 134
--- End of stack trace from previous location ---

Failures 5/20-7/19 (incl. PRs):

Day Run OS Runtime Namespace
6/29 PR #52237 Fedora.30.Amd64.Open Mono ConnectSync
6/29 Official run Ubuntu.1910.Amd64.Open CoreCLR ConnectEap
6/30 Official run Debian.9.Amd64.Open Mono ConnectSync
7/1 Official run SLES.15.Amd64.Open Mono ConnectSync
7/1 PR #54755 Debian.10.Amd64.Open CoreCLR ConnectTask
7/2 PR #55035 RedHat.7.Amd64.Open CoreCLR ConnectSync
7/2 PR #54845 RedHat.7.Amd64.Open CoreCLR ConnectCancellableTask
7/5 PR #55182 Debian.9.Amd64.Open Mono ConnectEap
7/9 PR #55354 Centos.8.Amd64.Open Mono ConnectCancellableTask
7/10 PR #54985 Ubuntu.1804.ArmArch.Open Mono ConnectTask
7/10 PR #55446 SLES.15.Amd64.Open Mono ConnectTask
7/12 PR #55499 SLES.15.Amd64.Open Mono ConnectTask
7/14 PR #55621 Centos.8.Amd64.Open Mono ConnectSync
7/14 Official run Ubuntu.1804.ArmArch.Open CoreCLR ConnectTask
7/14 PR #55644 Centos.8.Amd64.Open CoreCLR ConnectSyncForceNonBlocking
7/16 PR #55811 SLES.15.Amd64.Open Mono ConnectSync
7/16 PR #54845 SLES.15.Amd64.Open CoreCLR ConnectSync
7/17 Official run Debian.9.Amd64.Open CoreCLR ConnectSync
7/19 PR #55939 Debian.10.Amd64.Open Mono ConnectTask
7/19 PR #55916 Centos.8.Amd64.Open CoreCLR ConnectApm
7/19 PR #55956 Fedora.32.Amd64.Open Mono ConnectEap
7/19 PR #54845 Centos.8.Amd64.Open CoreCLR ConnectApm
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jul 15, 2021
@dotnet-issue-labeler
Copy link

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.

@ghost
Copy link

ghost commented Jul 16, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Runfo Tracking Issue: Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1237035 runtime Rolling net6.0-Linux-Release-arm64-CoreCLR_release-(Ubuntu.1804.ArmArch.Open)[email protected]/dotnet-buildtools/prereqs:ubuntu-16.04-helix-arm64v8-20210106155927-56c6673 console.log runclient.py
1234963 runtime Rolling net6.0-Linux-Release-x64-Mono_release-(Fedora.32.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:fedora-32-helix-20210710031120-870c408 console.log runclient.py
1232399 runtime PR 55499 net6.0-Linux-Debug-x64-Mono_release-SLES.15.Amd64.Open console.log runclient.py
1231144 runtime PR 55446 net6.0-Linux-Debug-x64-Mono_release-SLES.15.Amd64.Open console.log runclient.py
1230745 runtime Rolling net6.0-Linux-Release-x64-CoreCLR_release-SLES.15.Amd64.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 5 5
Author: runfoapp[bot]
Assignees: -
Labels:

area-Infrastructure-libraries, untriaged

Milestone: -

@safern
Copy link
Member

safern commented Jul 16, 2021

I think this is more a networking issue, the test is failing with:

System.Net.Sockets.Tests.ConnectTask.Connect_DualMode_DnsConnect_RetrievedEndPoints_Success [FAIL]
      System.Net.Sockets.SocketException : Transport endpoint is not connected
      Stack Trace:
        /_/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs(3712,0): at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
        /_/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs(355,0): at System.Net.Sockets.Socket.get_RemoteEndPoint()
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/Connect.cs(134,0): at System.Net.Sockets.Tests.Connect`1.Connect_DualMode_DnsConnect_RetrievedEndPoints_Success()
        --- End of stack trace from previous location ---
  Finished:    System.Net.Sockets.Tests
=== TEST EXECUTION SUMMARY ===
   System.Net.Sockets.Tests  Total: 1929, Errors: 0, Failed: 1, Skipped: 1, Time: 13.677s

@ghost
Copy link

ghost commented Jul 16, 2021

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

Runfo Tracking Issue: Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1237035 runtime Rolling net6.0-Linux-Release-arm64-CoreCLR_release-(Ubuntu.1804.ArmArch.Open)[email protected]/dotnet-buildtools/prereqs:ubuntu-16.04-helix-arm64v8-20210106155927-56c6673 console.log runclient.py
1234963 runtime Rolling net6.0-Linux-Release-x64-Mono_release-(Fedora.32.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:fedora-32-helix-20210710031120-870c408 console.log runclient.py
1232399 runtime PR 55499 net6.0-Linux-Debug-x64-Mono_release-SLES.15.Amd64.Open console.log runclient.py
1231144 runtime PR 55446 net6.0-Linux-Debug-x64-Mono_release-SLES.15.Amd64.Open console.log runclient.py
1230745 runtime Rolling net6.0-Linux-Release-x64-CoreCLR_release-SLES.15.Amd64.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 5 5
Author: runfoapp[bot]
Assignees: -
Labels:

area-System.Net.Sockets, untriaged

Milestone: -

@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Jul 20, 2021
@karelz karelz added this to the 6.0.0 milestone Jul 20, 2021
@karelz karelz added test-run-core Test failures in .NET Core test runs os-linux Linux OS (any supported distro) labels Jul 20, 2021
@karelz
Copy link
Member

karelz commented Jul 20, 2021

Looks like different manifestation of #54677 after attempted fix in PR #54681

@karelz karelz changed the title Connect_DualMode_DnsConnect_RetrievedEndPoints_Success test failure Connect_DualMode_DnsConnect_RetrievedEndPoints_Success - SocketException: Transport endpoint is not connected Jul 20, 2021
@karelz
Copy link
Member

karelz commented Jul 20, 2021

@tmds any further thoughts here and on the related issue which didn't disappear?

@karelz
Copy link
Member

karelz commented Jul 20, 2021

Test disabled on Linux in PR #56003 on 7/20

@karelz
Copy link
Member

karelz commented Jul 27, 2021

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:

Day Run
7/26 PR #56224
7/26 PR #55849
7/27 PR #56370
7/28 PR #56486
7/29 PR #56541
7/30 1x Official run + 1x PR #56559

cc @antonfirsov

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jul 27, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jul 30, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets disabled-test The test is disabled in source code against the issue os-linux Linux OS (any supported distro) test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants