[ci-scan] Skip SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds on Android (refs #128141)#128309
Draft
github-actions[bot] wants to merge 2 commits into
Conversation
…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>
Contributor
|
Tagging subscribers to this area: @karelz, @dotnet/ncl |
This was referenced May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reasoning
The test
ConnectAsync_WithBuffer_Succeedsconsistently fails on Android becauseIsSocketNonBlockingreturnsTrueafterConnectAsyncwith a buffer completes, while the test expectsFalse. 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):
SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeedsmatches exactlyAssert.False() Failureon theIsSocketNonBlockingcheckImpact on platforms
Errors log
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.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".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: