You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Note
🔒 Integrity filter blocked 1 item
The following item was blocked because it doesn't meet the GitHub integrity level.
#125825search_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:
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-arm64 Release AllSubsets_CoreCLR-System.Net.Sockets.Tests
Error Message
{ "ErrorMessage": ["SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds", "Assert.False() Failure"], "BuildRetry": false, "ExcludeConsoleLog": false }Failure details:
Affected legs:
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
ConnectAsyncwith a buffer reports the socket as still blocking (Blocking == true) after a successful async connect on Android. The test verifies that afterConnectAsyncwith a pre-connect buffer completes successfully, the socket'sBlockingproperty returnsfalse. This differs from the IPv6/Connection refused failures tracked in the now-closed #127986. Area owner:@dotnet/ncl.Note
🔒 Integrity filter blocked 1 item
The following item was blocked because it doesn't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Report
Summary