Skip to content

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

Merged
rzikm merged 2 commits into
mainfrom
ci-scan/skip-socket-blocking-android-128141-3d50a239d31dbd5b
May 27, 2026
Merged

[ci-scan] Skip SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on Android (refs #128141)#128584
rzikm merged 2 commits into
mainfrom
ci-scan/skip-socket-blocking-android-128141-3d50a239d31dbd5b

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Reasoning

The test SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds consistently fails on Android with Assert.False() Failure (Expected: False, Actual: True) on line 229 of Connect.Unix.cs. The socket ends up in non-blocking mode after ConnectAsync with a buffer on Android, contrary to the test's expectation that TFO/connectx would leave it blocking. The [ActiveIssue] annotation scoped to TestPlatforms.Android is the correct fix pending investigation.

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 in both KBE and current log
  3. Same OS: yes — Android in both
  4. Same architecture: yes — arm64/x64 both affected (KBE tracks android-arm64, current also fails on android-x64)

Impact on platforms

  • runtime-extra-platforms / android-arm64 Release AllSubsets_CoreCLR @ Windows.11.Amd64.Android.Open — exit code 1
  • runtime-extra-platforms / android-x64 Release NativeAOT @ 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

Linked issue

#128141

Note

🔒 Integrity filter blocked 3 items

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

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 · ● 47.1M ·

…ds on Android (refs #128141)

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.

@rzikm rzikm marked this pull request as ready for review May 27, 2026 11:36
Copilot AI review requested due to automatic review settings May 27, 2026 11:36
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

@rzikm rzikm merged commit 0d92fad into main May 27, 2026
87 of 93 checks passed
@rzikm rzikm deleted the ci-scan/skip-socket-blocking-android-128141-3d50a239d31dbd5b branch May 27, 2026 11:36
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.

2 participants