Skip to content

[browser][MT] WebSocket is already in CLOSING or CLOSED state #97260

Closed
@buyaa-n

Description

@buyaa-n

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=535317
Build error leg or test failing: WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution
Pull request: #97177

Error Message

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

{
  "ErrorMessage": "WebSocket is already in CLOSING or CLOSED state",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

From log:

[23:20:50] fail: [out of order message from the browser]: http://127.0.0.1:38015/_framework/dotnet.runtime.js 2 WebSocket is already in CLOSING or CLOSED state.
[23:20:50] info: [2024-01-20T23:20:50.279Z] [PASS] System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ServerInitiated_CanReceive(server: ws://127.0.0.1:38015/WebSocket/EchoWebSocket.ashx)
[23:20:50] info: [2024-01-20T23:20:50.281Z] [STRT] System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ServerInitiated_CanReceive(server: wss://127.0.0.1:41071/WebSocket/EchoWebSocket.ashx)
[23:20:50] fail: [out of order message from the browser]: http://127.0.0.1:38015/_framework/dotnet.runtime.js 2 WebSocket is already in CLOSING or CLOSED state.
[23:22:13] warn: MONO_WASM [0xdc19c-main]: WebSocket error {}
[23:22:13] fail: [out of order message from the browser]: http://127.0.0.1:38015/_framework/dotnet.runtime.js 2 WebSocket connection to 'ws://127.0.0.1:38015/WebSocket/EchoWebSocket.ashx?subprotocol=CustomProtocol' failed: Error during WebSocket handshake: Response must not include 'Sec-WebSocket-Protocol' header if not present in request: CustomProtocol
[23:22:13] info: [2024-01-20T23:22:13.323Z] [PASS] System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_PassNoSubProtocol_ServerRequires_ThrowsWebSocketException(server: ws://127.0.0.1:38015/WebSocket/EchoWebSocket.ashx)
[23:22:13] info: [2024-01-20T23:22:13.324Z] [STRT] System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_PassNoSubProtocol_ServerRequires_ThrowsWebSocketException(server: wss://127.0.0.1:41071/WebSocket/EchoWebSocket.ashx)
[23:22:13] warn: MONO_WASM [0xdc19c-main]: WebSocket error {}
[23:22:13] fail: [out of order message from the browser]: http://127.0.0.1:38015/_framework/dotnet.runtime.js 2 WebSocket connection to 'wss://127.0.0.1:41071/WebSocket/EchoWebSocket.ashx?subprotocol=CustomProtocol' failed: Error during WebSocket handshake: Response must not include 'Sec-WebSocket-Protocol' header if not present in request: CustomProtocol
[23:22:13] info: [2024-01-20T23:22:13.379Z] [PASS] System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_PassNoSubProtocol_ServerRequires_ThrowsWebSocketException(server: wss://127.0.0.1:41071/WebSocket/EchoWebSocket.ashx)
[23:22:13] info: [2024-01-20T23:22:13.382Z] [STRT] System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_CancellationRequestedAfterConnect_ThrowsOperationCanceledException
[23:22:13] warn: MONO_WASM [0xdc19c-main]: WebSocket error {}
[23:22:13] fail: [out of order message from the browser]: http://127.0.0.1:38015/_framework/dotnet.runtime.js 2 WebSocket connection to 'ws://127.0.0.1:43179/' failed: Connection closed before receiving a handshake response

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=535317
Error message validated: WebSocket is already in CLOSING or CLOSED state
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 1/23/2024 10:27:54 AM UTC

Report

Build Definition Test Pull Request
603285 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #99703
602501 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98858
591649 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #99349
591783 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #99347
590127 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #99327
583366 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #99070
580589 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #95001
579201 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98802
578246 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98852
576845 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98802
576320 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98802
575939 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98802
575598 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98802
574940 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution #98118

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 13

Metadata

Metadata

Assignees

Labels

Known Build ErrorUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architecturearea-System.Netblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'os-browserBrowser variant of arch-wasm

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions