Skip to content

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

Draft
github-actions[bot] wants to merge 2 commits into
mainfrom
ci-scan/disable-socket-blocking-android-128141-665bc830611e8dfe
Draft

[ci-scan] Skip SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on Android (refs #128141)#128309
github-actions[bot] wants to merge 2 commits into
mainfrom
ci-scan/disable-socket-blocking-android-128141-665bc830611e8dfe

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Reasoning

The test ConnectAsync_WithBuffer_Succeeds consistently fails on Android because IsSocketNonBlocking returns True after ConnectAsync with a buffer completes, while the test expects False. The test already has Android-specific logic (line 227) but the condition does not cover this case correctly.

The [ActiveIssue] attribute is the right fix because it narrows the skip to Android only, matching the observed failure scope.

Linked KBE: #128141

Match verification (from Step 4.8):

  1. Same test/family: yes — SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds matches exactly
  2. Same failure signature: yes — Assert.False() Failure on the IsSocketNonBlocking check
  3. Same OS: yes — Android
  4. Same architecture: yes — arm64 (android-arm64 Release AllSubsets_CoreCLR)

Impact on platforms

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

First build it occurred

Linked issue

#128141

Note

🔒 Integrity filter blocked 2 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".
  • #115479 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 · ● 49.8M ·

…ds on Android (refs #128141)

The test consistently fails on Android with Assert.False() Failure because
IsSocketNonBlocking returns True unexpectedly after ConnectAsync with buffer.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dotnet-policy-service
Copy link
Copy Markdown
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants