Skip to content

[ci-scan] Known Build Error: System.Net.Sockets DualMode IPv6 tests fail on Android with Connection refused #127986

Description

@github-actions

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1413202
Build error leg or test failing: android-arm64 Release AllSubsets_Mono - System.Net.Sockets.Tests

Error Message

{
  "ErrorMessage": ["DualModeConnect", "System.Net.Sockets.SocketException : Connection refused"],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Tracking: #127565

Summary: System.Net.Sockets dual-mode IPv6 socket tests fail on Android with "Connection refused" when connecting to IPv6 loopback (::1). The Android emulator environment lacks proper IPv6 support. Failing tests:

  • DualModeConnectToHostString.DualModeConnect_LoopbackDnsToHost_Helper(::1, False)
  • DualModeConnectToDnsEndPoint.DualModeConnect_DnsEndPointToHost_Helper(::1, False)
  • DualModeConnectAsync.DualModeConnectAsync_DnsEndPointToHost_Helper(::1, False)
  • SocketAsyncEventArgsTest.Connect_Parallel_FailsOver(preferIPv6: True)
  • SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds

This is an infrastructure/environment issue, not a product bug. Failures present across all Android architectures (arm64, x64, x86) in every recent extra-platforms build.

Recommended action: Add [ActiveIssue] on TestPlatforms.Android for the IPv6 DualMode tests in src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs.

Note

🔒 Integrity filter blocked 19 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #125901 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #122311 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #114055 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #120891 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #84006 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #112841 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #83317 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #51317 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #86416 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #90084 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #77241 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #115319 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #93768 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #96506 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #90803 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #126682 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • ... and 3 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 35.9M · ◷

Activity

  1. dotnet-policy-service commented on May 11, 2026

    @dotnet-policy-service
    Contributor

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

  2. kotlarmilos commented on May 12, 2026

    @kotlarmilos
    Member

    Tracked in #127565

  3. locked and limited conversation to collaborators on Jun 12, 2026
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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions