Repository navigation
Test failure: System.Net.WebSockets.Client.Tests.ConnectTest_SharedHandler_Loopback.ConnectAsync_CancellationRequestedAfterConnect_ThrowsOperationCanceledException #133225
Copy link
Copy link
Closed as not planned
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabPriority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-System.Netblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Milestone
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1574106&view=results
Build error leg or test failing: System.Net.WebSockets.Client.Tests.ConnectTest_SharedHandler_Loopback.ConnectAsync_CancellationRequestedAfterConnect_ThrowsOperationCanceledException
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "System.Net.Sockets.SocketException : An existing connection was forcibly closed by the remote host.",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 189 | 268 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabPriority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-System.Netblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Activity
dotnet-policy-service commentedon Sep 4, 2026
Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
rzikm commentedon Sep 18, 2026
The pattern matches different test failure than mentioned in the title, so I am going to close this issue, the matched issue is tracked by #133778