Skip to content

WasmTestOnBrowser-System.Private.Xml.Tests - GENERAL_FAILURE #76134

Closed

Description

@karelz

Runfo failures in last 30 days

  • Platform: net7.0-Browser-Release-wasm-Mono_Release-WasmTestOnBrowser-(Windows.Amd64.Server2022.Open)windows.amd64.server2022.open
Day Run Details
9/23 Rolling run 28100 Console - InvalidOperationException
9/21 Rolling run 24630 Console - InvalidOperationException
9/20 2x Rolling run 24096 Console & Console - InvalidOperationException
9/20 Rolling run 23279 Console - InvalidOperationException
9/19 Rolling run 22721 Console - InvalidOperationException
9/18 Rolling run 21535 Console - ChannelClosedException
9/17 Rolling run 21283 Console - ChannelClosedException
9/16 Rolling run 20550 Console - ChannelClosedException
9/16 Rolling run 19690 Console - ChannelClosedException
9/15 Rolling run 18995 Console - ChannelClosedException

Failure examples:

InvalidOperationException - Console on 9/23:

[23:37:33] info: Starting:    System.Private.Xml.Tests.dll
[23:38:40] fail: 224964280
[23:38:40] fail: 224964280
[23:38:40] fail: 224964280
[23:38:40] fail: 225333728
[23:38:40] info: WASM EXIT 1
[23:38:40] info: Waiting to flush log messages with a timeout of 120 secs ..
[23:38:40] info: WASM EXIT 1
[23:38:40] fail: Application has finished with exit code TESTS_FAILED but 0 was expected
fail: Microsoft.AspNetCore.Server.Kestrel[13]
      Connection id "0HMKTNI0N1333", Request id "0HMKTNI0N1333:00000001": An unhandled exception was thrown by the application.
      System.InvalidOperationException: Message processor is not running. Make sure to call RunAsync first
         at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.InvokeAsync(String message, Boolean isError) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 94
         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 196
         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 163
      --- 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)
XHarness exit code: 71 (GENERAL_FAILURE)

C:\helix\work\workitem\e\wasm_build\AppBundle>set EXIT_CODE=71 
----- end Fri 09/23/2022 23:38:44.97 ----- exit code 71 ----------------------------------------------------------

ChannelClosedException - Console on

[23:13:04] info: Starting:    System.Private.Xml.Tests.dll
[23:14:16] fail: 245597000
[23:14:16] fail: 245597000
[23:14:16] fail: 245597000
[23:14:16] fail: 245597120
[23:14:16] info: WASM EXIT 1
[23:14:16] info: Waiting to flush log messages with a timeout of 120 secs ..
[23:14:16] info: WASM EXIT 1
[23:14:16] fail: Flushing log messages failed with: System.InvalidOperationException: An attempt was made to transition a task to a final state when it had already completed.
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.ProcessMessage(String message, Boolean isError) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 200
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.RunAsync(CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 82
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.RunAsync(CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 82
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.CompleteAndFlushAsync(Nullable`1 timeout) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 106. Ignoring.
fail: Microsoft.AspNetCore.Server.Kestrel[13]
      Connection id "0HMKPPD0JB2H6", Request id "0HMKPPD0JB2H6:00000001": An unhandled exception was thrown by the application.
      System.Threading.Channels.ChannelClosedException: The channel has been closed.
         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 196
         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 163
      --- 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)
[23:14:16] fail: [out of order message from the browser]: http://127.0.0.1:49195/dotnet.js 4:1872 "[main] websocket closed: [object CloseEvent]" CloseEvent
[23:14:16] info: Could not process message: {"method":"console.log","payload":"WASM EXIT 1","arguments":["WASM EXIT 1"]}
[23:14:16] info: Application has finished with exit code TESTS_FAILED. But the log processor failed with GENERAL_FAILURE.
[23:14:16] fail: Application has finished with exit code GENERAL_FAILURE but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

C:\helix\work\workitem\e\wasm_build\AppBundle>set EXIT_CODE=71 
----- end Sun 09/18/2022 23:14:20.41 ----- exit code 71 ----------------------------------------------------------

Report

Summary

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

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Sep 24, 2022
  2. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Sep 24, 2022
  3. radical commented on Sep 26, 2022

    @radical
    Member

    The xharness exception can be ignored. The real issue is #74302 .

  4. lewing commented on Sep 26, 2022

    @lewing
    Member

    looks like a manifestation of #74302

  5. removed
    untriagedNew issue has not been triaged by the area owner
    on Sep 26, 2022
  6. modified the milestones: 7.0.0, 7.0.x on Sep 26, 2022
  7. carlossanlop commented on Oct 5, 2022

    @carlossanlop
    Contributor

    It's affecting various System.Xml tests. They all show this error message:

    [21:36:12] warn: Blocking on the main thread is very dangerous, see https://emscripten.org/docs/porting/pthreads.html#blocking-on-the-main-browser-thread
    [21:51:05] fail: Tests timed out. Killing driver service pid 4661
    [21:51:06] fail: Application has finished with exit code TIMED_OUT but 0 was expected
    XHarness exit code: 71 (GENERAL_FAILURE)
    
  8. radical commented on Oct 5, 2022

    @radical
    Member

    Ignore all the failures in these two:

    • Build Browser wasm Linux Release LibraryTests_Threading
    • Build Browser wasm Linux Release LibraryTests_Threading_PerfTracing

    The job is orange because we want to ignore the test failures. It will be red for build failures though, and those we are interested in.

  9. lewing commented on Oct 14, 2022

    @lewing
    Member

    we think this is fixed in mail now so please make noise if you see it in a test

  10. ghost locked as resolved and limited conversation to collaborators on Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

arch-wasmWebAssembly architecturearea-VM-meta-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions