[ci-scan] Skip Android DualMode IPv6 socket tests (Connection refused on ::1)

[github-actions]

Caution

Security scanning requires review for CI Outer-Loop Failure Scanner

Details

The threat detection results could not be parsed. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

Summary

Mute DualMode IPv6 socket tests on Android. Android emulators don't support IPv6 loopback, causing Connection refused on ::1.

Linked KBE: #127986
Tracking: #127565

Changes

• DualModeSocketTest.cs: Add [ActiveIssue("...127986", TestPlatforms.Android)] to DualModeConnectToHostString, DualModeConnectToDnsEndPoint, and DualModeConnectAsync classes.
• SocketAsyncEventArgsTest.cs: Add [ActiveIssue("...127986", TestPlatforms.Android)] to Connect_Parallel_FailsOver.

Reasoning

1. Same test? Yes — DualMode IPv6 socket tests match KBE.
2. Same failure signature? Yes — Connection refused [::1].
3. Same OS? Yes — Android.
4. Same architecture? Yes — arm64 (Android emulator).

Failing legs

• runtime-extra-platforms (def 154): Android arm64 device tests
• Recurring across multiple builds on main

Note

This PR was generated by an automated CI scan workflow using GitHub Copilot.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #114222 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

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 · ● 45.9M · ◷

[dotnet-policy-service]

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