Skip to content

[6.0] CI test failure in OSX System.Net.Sockets.Tests.DualModeAccept.AcceptV4BoundToAnyV6_Success [FAIL] #81437

Description

@buyaa-n

Found in a release/6.0 backport PR. https://github.com/dotnet/runtime/pull/81281/checks?check_run_id=10937030682

Log: https://helix.dot.net/api/2019-06-17/jobs/1dacef47-5173-49ec-ac68-fc7446cf11ed/workitems/System.Net.Sockets.Tests/console

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(1092,0): at System.Net.Sockets.Socket.Accept()
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs(766,0): at System.Net.Sockets.Tests.DualModeAccept.Accept_Helper(IPAddress listenOn, IPAddress connectTo)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs(756,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
=== TEST EXECUTION SUMMARY ===
   System.Net.Sockets.Tests  Total: 1888, Errors: 0, Failed: 1, Skipped: 1, Time: 5.332s

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Jan 31, 2023
  2. antonfirsov commented on Feb 2, 2023

    @antonfirsov
    Contributor

    Triage: we should keep monitoring if it happens again. We would only fix it if it fails massively, in that case we shall reprioritize.

  3. removed
    untriagedNew issue has not been triaged by the area owner
    on Feb 2, 2023
  4. added this to the Future milestone on Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions