Build Information

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

Error Message

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

Failure details:

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

Affected legs:

• runtime-extra-platforms / android-arm64 Release AllSubsets_CoreCLR @ Windows.11.Amd64.Android.Open

Console Log: https://helixr1107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-6857124bf4db499c94/System.Net.Sockets.Tests/3/console.fdc26615.log?helixlogtype=result

First build in window: runtime-extra-platforms 20260512.1 (2026-05-12). Confirmed in at least 2 consecutive builds (May 12, May 13). This is within the scanned window and may not be the true origin.

Recommended action: Investigate why ConnectAsync with a buffer reports the socket as still blocking (Blocking == true) after a successful async connect on Android. The test verifies that after ConnectAsync with a pre-connect buffer completes successfully, the socket's Blocking property returns false. This differs from the IPv6/Connection refused failures tracked in the now-closed #127986. Area owner: @dotnet/ncl.

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

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

Report

Summary