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

CI: System.ArgumentException : The supplied System.Net.Internals.SocketAddress is an invalid size for the System.Net.IPEndPoint end point. #40913

Closed
benaadams opened this issue Aug 17, 2020 · 6 comments
Labels
area-System.Net.Sockets bug os-mac-os-x macOS aka OSX test-run-core Test failures in .NET Core test runs
Milestone

Comments

@benaadams
Copy link
Member

Libraries Test Run release coreclr OSX x64 Debug failed

/private/tmp/helix/working/C0070A33/w/AA2A094E/e /private/tmp/helix/working/C0070A33/w/AA2A094E/e
  Discovering: System.Net.Sockets.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Sockets.Tests (found 816 of 1231 test cases)
  Starting:    System.Net.Sockets.Tests (parallel test collections = on, max threads = 4)
    System.Net.Sockets.Tests.DualModeAccept.AcceptV4BoundToAnyV6_Success [FAIL]
      System.ArgumentException : The supplied System.Net.Internals.SocketAddress is an invalid size for the System.Net.IPEndPoint end point. (Parameter 'socketAddress')
      Stack Trace:
        /_/src/libraries/Common/src/System/Net/Internals/IPEndPointExtensions.cs(36,0): at System.Net.Sockets.IPEndPointExtensions.Create(EndPoint thisObj, SocketAddress socketAddress)
        /_/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs(1116,0): at System.Net.Sockets.Socket.Accept()
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs(765,0): at System.Net.Sockets.Tests.DualModeAccept.Accept_Helper(IPAddress listenOn, IPAddress connectTo)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs(755,0): at System.Net.Sockets.Tests.DualModeAccept.AcceptV4BoundToAnyV6_Success()
    System.Net.Sockets.Tests.CreateSocket.Ctor_Raw_Supported_Success [SKIP]
      Condition(s) not met: "SupportsRawSockets"
  Finished:    System.Net.Sockets.Tests

https://helix.dot.net/api/2019-06-17/jobs/cbdca4c0-455d-445a-b4be-f66a996ae91b/workitems/System.Net.Sockets.Tests/console

Seen in #40877

https://dev.azure.com/dnceng/public/_build/results?buildId=773532&view=logs&jobId=4724cd84-0a26-56bc-9b1d-ca1983f340b0&j=4724cd84-0a26-56bc-9b1d-ca1983f340b0&t=522fb2d8-007e-5c8a-7842-66e99f004601

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-System.Net.Sockets untriaged New issue has not been triaged by the area owner labels Aug 17, 2020
@ghost
Copy link

ghost commented Aug 17, 2020

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

@scalablecory scalablecory added this to the 5.0.0 milestone Aug 17, 2020
@scalablecory scalablecory added bug and removed untriaged New issue has not been triaged by the area owner labels Aug 17, 2020
@karelz karelz added the os-mac-os-x macOS aka OSX label Aug 18, 2020
@karelz
Copy link
Member

karelz commented Aug 18, 2020

Triage: Single occurrence in last 3-6 months.
We should assess if it is a regression in 5.0 - we changed the code around it. The failure is suspicious.
If we don't have anything useful, ok to punt it to 6.0.

@wfurt
Copy link
Member

wfurt commented Aug 18, 2020

The relevant code is:

          if (family == AddressFamily.InterNetwork || family == AddressFamily.InterNetworkV6)
            {
                if (socketAddress.Size < 8)
                {
                    throw new ArgumentException(SR.Format(SR.net_InvalidSocketAddressSize, socketAddress.GetType().FullName, thisObj.GetType().FullName), nameof(socketAddress));
                }

                return socketAddress.GetIPEndPoint();
            }

@karelz
Copy link
Member

karelz commented Aug 25, 2020

Triage: @MihaZupan can you please look at test history? Thanks!

@karelz karelz modified the milestones: 5.0.0, 6.0.0 Aug 25, 2020
@MihaZupan
Copy link
Member

Only one failure in history - on the linked PR.

@karelz karelz added the test-run-core Test failures in .NET Core test runs label May 4, 2021
@karelz
Copy link
Member

karelz commented May 10, 2021

No failure between 2/23-5/10 (incl. PRs). Closing.

@karelz karelz closed this as completed May 10, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jun 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets bug os-mac-os-x macOS aka OSX test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

No branches or pull requests

6 participants