-
Notifications
You must be signed in to change notification settings - Fork 5.4k
[wasm][debugger] ArrayTests timing out on helix #62661
Copy link
Copy link
Closed
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-Debugger-monodisabled-testThe test is disabled in source code against the issueThe test is disabled in source code against the issue
Description
It manages to connect to the proxy, but the Inspector doesn't seem to resume executing. It's likely blocking somewhere due to not using ConfigureAwait(false).
[23:21:20] info: DebuggerTests.Inspector[0] -- OpenSessionAsync: Client.Connect launch-chrome-and-connect
[23:21:20] dbug: Microsoft.WebAssembly.Diagnostics.InspectorClient[0] connecting to ws://localhost:9400/launch-chrome-and-connect
[23:21:20] info: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] New test request
[23:21:20] trce: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] browser-stderr:
[23:21:20] trce: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] browser-stderr: DevTools listening on ws://127.0.0.1:44177/devtools/browser/c6c22a16-0e15-4123-825f-5f5a0202248d
[23:21:20] trce: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] browser-stderr: [1210/232120.680043:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[23:21:20] trce: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] res is [ { "description": "", "devtoolsFrontendUrl": "/devtools/inspector.html?ws=127.0.0.1:44177/devtools/page/909B20C5945B78E3DA34FAB976EF59DA", "id": "909B20C5945B78E3DA34FAB976EF59DA",
[23:21:20] trce: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] >>> ws://127.0.0.1:44177/devtools/page/909B20C5945B78E3DA34FAB976EF59DA
[23:21:20] info: Microsoft.WebAssembly.Diagnostics.TestHarnessProxy[0] launching proxy for ws://127.0.0.1:44177/devtools/page/909B20C5945B78E3DA34FAB976EF59DA
[23:21:20] dbug: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] DevToolsProxy: Starting on ws://127.0.0.1:44177/devtools/page/909B20C5945B78E3DA34FAB976EF59DA
[23:21:20] dbug: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] DevToolsProxy: IDE waiting for connection on ws://127.0.0.1:44177/devtools/page/909B20C5945B78E3DA34FAB976EF59DA
[23:21:20] dbug: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] DevToolsProxy: Client connected on ws://127.0.0.1:44177/devtools/page/909B20C5945B78E3DA34FAB976EF59DA
[23:21:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:22:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:22:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:23:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:23:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:24:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:24:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:25:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:25:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:26:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:26:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:27:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:27:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:28:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:28:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:29:20] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
[23:29:50] info: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] ---------------------------- Proxy state ----------------------- Commands sent, and waiting for response: 0 Messages received, waiting for IDE/proxy to respond: 0 ----------------------------------------
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-Debugger-monodisabled-testThe test is disabled in source code against the issueThe test is disabled in source code against the issue