Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[browser][MT] WasmBrowserTestRunner.RunConsoleMessagesPump - abrupt disconect #101618

Closed
kunalspathak opened this issue Apr 26, 2024 · 3 comments
Closed
Labels
arch-wasm WebAssembly architecture area-System.Net.Http area-VM-threading-mono Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@kunalspathak
Copy link
Member

kunalspathak commented Apr 26, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=657270
Build error leg or test failing: WasmTestOnChrome-MT-System.Net.Http.Functional.Tests.WorkItemExecution
Pull request: #101188

Error Message

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

{
  "ErrorMessage": "The remote party closed the WebSocket connection without completing the close handshake",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=657270
Error message validated: [The remote party closed the WebSocket connection without completing the close handshake]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/26/2024 6:13:23 PM UTC

Report

Build Definition Test Pull Request
768949 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106091
769545 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106123
769495 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106119
769366 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #103153
769322 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105836
769299 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106108
768750 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #104964
769093 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105663
768879 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105841
768837 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106040
768855 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105661
768637 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105839
768671 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106080
768664 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106078
768615 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106075
768349 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #99596
768432 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105879
768415 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106014
768409 dotnet/runtime Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.FirstRunGeneratesTableAndSecondRunLoadsIt(config: "Release") #106070
768189 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106059
768165 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106053
768078 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #106030
767917 dotnet/runtime System.Net.WebSockets.Client.Tests.AbortTest_Invoker_Http2.ServerResetsAfterCloseHandshake_NoExceptionOnClient #105841
767792 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #104393
767790 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #104817
764038 dotnet/runtime Workloads-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105802
763989 dotnet/runtime Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105868
763929 dotnet/runtime Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105841
763869 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105559
763492 dotnet/runtime Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105844
763348 dotnet/runtime Workloads-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #104393
763392 dotnet/runtime System.Net.WebSockets.Client.Tests.KeepAliveTest_Invoker_Http2.KeepAlive_LongDelayBetweenSendReceives_Succeeds #105841
763314 dotnet/runtime Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution
763107 dotnet/runtime Workloads-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105826
761188 dotnet/runtime Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105734
761045 dotnet/runtime Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105119
760318 dotnet/runtime Workloads-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105696
760177 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105464
760243 dotnet/runtime Workloads-ST-Wasm.Build.Tests.TestAppScenarios.InterpPgoTests.WorkItemExecution #105471
758744 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution #105559

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 40
@kunalspathak kunalspathak added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Apr 26, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 26, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 26, 2024
@jeffschwMSFT jeffschwMSFT added arch-wasm WebAssembly architecture area-System.Net.Http labels May 1, 2024
Copy link
Contributor

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

@lewing lewing removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label May 2, 2024
@lewing lewing added this to the 9.0.0 milestone May 2, 2024
@lewing lewing added area-VM-threading-mono and removed untriaged New issue has not been triaged by the area owner needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels May 2, 2024
@pavelsavara
Copy link
Member

This is complaint by the xharness which is hosting the web server.
It doesn't mean that the test failed.
It's probably caused by WebWorker being killed while the web-socket which is shipping console log is still open.

I think we should just silence the xharness WasmBrowserTestRunner.RunConsoleMessagesPump is such case or make it just warning.

fail: Microsoft.AspNetCore.Server.Kestrel[13]
      Connection id "0HN4RQAG12KRC", Request id "0HN4RQAG12KRC:00000001": An unhandled exception was thrown by the application.
      System.Net.WebSockets.WebSocketException (2): The remote party closed the WebSocket connection without completing the close handshake.
         at System.Net.WebSockets.ManagedWebSocket.ThrowEOFUnexpected()
         at System.Net.WebSockets.ManagedWebSocket.EnsureBufferContainsAsync(Int32 minimumRequiredBytes, CancellationToken cancellationToken)
         at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
         at System.Net.WebSockets.ManagedWebSocket.ReceiveAsyncPrivate[TResult](Memory`1 payloadBuffer, CancellationToken cancellationToken)
         at System.Net.WebSockets.ManagedWebSocket.ReceiveAsyncPrivate[TResult](Memory`1 payloadBuffer, CancellationToken cancellationToken)
         at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
         at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
      --- End of stack trace from previous location ---
         at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmBrowserTestRunner.RunConsoleMessagesPump(WebSocket socket, CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmBrowserTestRunner.cs:line 174
         at Microsoft.DotNet.XHarness.CLI.Commands.WebServer.TestWebServerStartup.<>c__DisplayClass3_0.<<Configure>b__2>d.MoveNext() in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WebServer.cs:line 174
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
         at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

@pavelsavara pavelsavara changed the title browser-Release-wasm-Mono_Release-WasmTestOnChrome fails with WebSocketException [browser][MT] WasmBrowserTestRunner.RunConsoleMessagesPump - abrupt disconect Jul 4, 2024
pavelsavara added a commit to pavelsavara/xharness that referenced this issue Jul 11, 2024
ivanpovazan pushed a commit to dotnet/xharness that referenced this issue Jul 15, 2024
@lewing lewing modified the milestones: 9.0.0, 10.0.0 Jul 31, 2024
@ilonatommy
Copy link
Member

No failures after the fix: dotnet/xharness#1231.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-System.Net.Http area-VM-threading-mono Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

No branches or pull requests

5 participants