[ci-scan] Skip SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on Android (refs #128141)

[github-actions]

Reasoning

The test SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds consistently fails on Android with Assert.False() Failure (Expected: False, Actual: True) at the IsSocketNonBlocking(client) assertion. On Android, the socket's non-blocking state after ConnectAsync with a buffer differs from what the test expects. The existing code at line 227 already special-cases Android (expecting the socket to NOT be non-blocking), but the assertion still fails on NativeAOT Android builds. The [ActiveIssue] attribute is the correct mechanism to skip this test while it's being investigated.

Linked KBE: #128141

Match verification (from Step 4.8):

1. Same test/family: yes — SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds
2. Same failure signature: yes — Assert.False() Failure at Connect.Unix.cs:line 229
3. Same OS: yes — Android (KBE covers android-arm64; this also affects android-x64)
4. Same architecture: yes — KBE title says "on Android" broadly, covering all Android architectures

Impact on platforms

• runtime-extra-platforms / android-x64 Release NativeAOT @ Windows.11.Amd64.Android.Open, exit code 1
• runtime-extra-platforms / android-arm64 Release AllSubsets_CoreCLR @ Windows.11.Amd64.Android.Open, exit code 1

Errors log

[FAIL] System.Net.Sockets.Tests.SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds
Assert.False() Failure
Expected: False
Actual:   True
   at System.Net.Sockets.Tests.SocketBlockingModeTransitionTests.<ConnectAsync_WithBuffer_Succeeds>d__10.MoveNext() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/Connect.Unix.cs:line 229

First build it occurred

• Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1416787
• Finished: 2026-05-12 (per KBE [ci-scan] Known Build Error: SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on Android #128141)
• Occurrences in window: 35+ (per KBE tracking)
• Persistent across the entire scanned window; true origin may predate 2026-05-12.

Linked issue

#128141

Note

🔒 Integrity filter blocked 6 items

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

• #125825 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [ci-scan] Known Build Error: SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on Android #128141 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #115508 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #114358 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #104841 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #62267 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 · ● 44.6M · ◷

[dotnet-policy-service]

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