System.Net.WebSockets.Client.Tests android fails

Open
#119,520 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, csharp
Domain
mobile, networking, testing-qa

Research direction

Start with the linked Azure build and the System.Net.WebSockets.Client.Tests.WorkItemExecution failure on Android. Review the known-issue guidance and the referenced pull request for context, then inspect the failing test logs. Done means the Android test work item completes successfully without command exit 70.

Written by the indexing model from the issue text.

Description

area-System.Net Known Build Error os-android

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1141856
Build error leg or test failing: System.Net.WebSockets.Client.Tests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime/pull/119453

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "['System.Net.WebSockets.Client.Tests' END OF WORK ITEM LOG: Command exited with 70]",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1141856
Error message validated: [['System.Net.WebSockets.Client.Tests' END OF WORK ITEM LOG: Command exited with 70]]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/10/2025 7:24:53 AM UTC

Report
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.