[ci-scan] Test failure: SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on android-x64

[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.

Build Information

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

Error Message

{
  "ErrorMessage": ["SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds", "Assert.False() Failure"],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Additional Context

Summary: System.Net.Sockets.Tests.SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds fails on android-x64 (Mono) with Assert.False() Failure (Expected: False, Actual: True). The test checks that Socket.Blocking is false after a successful ConnectAsync with a buffer, but the socket remains in blocking mode on Android.

Failed in (2+):

• runtime-extra-platforms 1418286 (2026-05-13)
• runtime-extra-platforms 1414719 (2026-05-10)

Console Log: https://helix.dot.net/api/2019-06-17/jobs/f1bd151a-aed7-47db-9d08-abc619b9ab2b/workitems/System.Net.Sockets.Tests/console

Error excerpt:

[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()

Impact on platforms:

• runtime-extra-platforms + android-x64 + Ubuntu.2204.Amd64.Android.29.Open + Mono + exit code 1

First build it occurred: Build 1414719 (2026-05-10) is the earliest in the scanned window. This is within the scanned window and may not be the true origin.

Tracking: #127645 (related iossimulator build breaks on same pipeline)

Recommended action: The socket blocking mode transition behavior differs on Android. The area owners (System.Net.Sockets) should investigate whether this is a platform limitation or a Mono-specific bug in the socket implementation on Android.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• dotnet.github.io

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "dotnet.github.io"

See Network Configuration for more information.

Note

🔒 Integrity filter blocked 1 item

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

• #125825 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 · ● 39.1M · ◷

Report

Build	Definition	Test	Pull Request
1420047	dotnet/runtime	System.Net.Sockets.Tests.WorkItemExecution
1418805	dotnet/runtime	System.Net.Sockets.Tests.WorkItemExecution	#124173

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
2	2	2

[rzikm]

Duplicate of #125825

@kotlarmilos this looks the same as #128141 but for different platform, looks like duplicate detection could be improved

[kotlarmilos]

Duplicate of #125825

@kotlarmilos this looks the same as #128141 but for different platform, looks like duplicate detection could be improved

Thanks, the dedup search did find #125825, but the MCP integrity guard stripped it from the result. The workflow runs with min-integrity: approved, and #125825 was opened by MatousBot which isn't associated with the repository

The #128141 wasn't found because the queries are keyed on the test name and the Known Build Error label, not on the broader runtime-extra-platforms + Mono/Android signature that links the two.

In the next iteration, I will update the workflow to broaden the dedup queries to also match by test class (SocketBlockingModeTransitionTests) and area label (area-System.Net.Sockets) so sibling failures across platforms get linked.