runtime icon indicating copy to clipboard operation
runtime copied to clipboard

WasmTestOnBrowser-System.Net.WebSockets.Client.Tests failed on browser-wasm linux Release LibraryTests_Threading_Smoke CI leg

Open buyaa-n opened this issue 1 year ago • 3 comments

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: https://github.com/dotnet/runtime/pull/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: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=535317 Error message validated: WebSocket is already in CLOSING or CLOSED state Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 1/23/2024 10:27:54 AM UTC

Report

Build Definition Test Pull Request
545890 dotnet/runtime WasmTestOnBrowser-System.Net.Http.Functional.Tests.WorkItemExecution dotnet/runtime#97696
535319 dotnet/runtime WasmTestOnBrowser-System.Threading.Tasks.Parallel.Tests.WorkItemExecution dotnet/runtime#97270
535337 dotnet/runtime Workloads-Wasm.Build.Tests.BuildPublishTests.WorkItemExecution dotnet/runtime#97096
535317 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97270
535095 dotnet/runtime WasmTestOnBrowser-System.Numerics.Tensors.Tests.WorkItemExecution dotnet/runtime#97282
535009 dotnet/runtime WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution dotnet/runtime#97270
534977 dotnet/runtime WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution dotnet/runtime#97270
534656 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97177
534478 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97152
534443 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97098
534303 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#96941
534263 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97192

Summary

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

buyaa-n avatar Jan 21 '24 02:01 buyaa-n

Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.

Issue Details

Build Information

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

Error Message

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

{
  "ErrorMessage": "out of order message from the browser",
  "ErrorPattern": "",
  "BuildRetry": false,
  "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
Author: buyaa-n
Assignees: -
Labels:

area-System.Net, blocking-clean-ci, Known Build Error

Milestone: -

ghost avatar Jan 21 '24 02:01 ghost

Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.

Issue Details

Build Information

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

Error Message

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

{
  "ErrorMessage": "out of order message from the browser",
  "ErrorPattern": "",
  "BuildRetry": false,
  "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: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=534656 Error message validated: out of order message from the browser Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 1/21/2024 2:21:15 AM UTC

Report

Build Definition Test Pull Request
535319 dotnet/runtime WasmTestOnBrowser-System.Threading.Tasks.Parallel.Tests.WorkItemExecution dotnet/runtime#97270
535337 dotnet/runtime Workloads-Wasm.Build.Tests.BuildPublishTests.WorkItemExecution dotnet/runtime#97096
535317 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97270
535095 dotnet/runtime WasmTestOnBrowser-System.Numerics.Tensors.Tests.WorkItemExecution dotnet/runtime#97282
535009 dotnet/runtime WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution dotnet/runtime#97270
534977 dotnet/runtime WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution dotnet/runtime#97270
534656 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97177
534478 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97152
534443 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97098
534303 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#96941
534263 dotnet/runtime WasmTestOnBrowser-System.Net.WebSockets.Client.Tests.WorkItemExecution dotnet/runtime#97192

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
6 11 11
Author: buyaa-n
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Net, blocking-clean-ci, untriaged, Known Build Error, os-browser

Milestone: -

ghost avatar Jan 22 '24 14:01 ghost

I updated the search filter because out of order message from the browser is too generic and happens even when everything is OK.

pavelsavara avatar Jan 22 '24 15:01 pavelsavara

@ilonatommy do we know what fixed this ?

pavelsavara avatar Mar 21 '24 20:03 pavelsavara

Most probably the fact that we used to reject all the attempts to receive when the socket was closed and now we keep letting the receive request to pass as long as there is indeed something in the buffer to be received, regardless of the WS state. https://github.com/dotnet/runtime/pull/99612

ilonatommy avatar Mar 22 '24 10:03 ilonatommy