[wasm] add support for retrying debugger tests when chrome launch times out #76528

karelz · 2022-10-03T10:02:22Z

Affected test:

DebuggerTests.SetVariableValueTests.DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange

Error: System.IO.IOException : [testId: 650] Timed out after 20s waiting for the browser to be ready: C:\helix\work\correlation\chrome-win\chrome.exe

Runfo failures in last 30 days as of 10/3:

Day	Run	Details
9/30	Rolling run 36814	net7.0-Browser-Release-wasm-Mono_chrome_Release-WasmDebuggerTests-(Windows.Amd64.Server2022.Open)windows.amd64.server2022.open
9/27	Rolling run 32310	net7.0-Browser-Release-wasm-Mono_chrome_Release-WasmDebuggerTests-(Windows.Amd64.Server2022.Open)windows.amd64.server2022.open

Error example from Console log:

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
OpenSession crashing. proxy state: RunLoopExitState { reason = Exception, exception = System.IO.IOException: [testId: 650] Timed out after 20s waiting for the browser to be ready: C:\helix\work\correlation\chrome-win\chrome.exe
   at DebuggerTests.WasmHostProvider.LaunchHostAsync(ProcessStartInfo psi, HttpContext context, Func`2 checkBrowserReady, String messagePrefix, Int32 hostReadyTimeoutMs, CancellationToken token) in /_/src/mono/wasm/debugger/DebuggerTestSuite/WasmHostProvider.cs:line 91
   at DebuggerTests.ChromeProvider.StartBrowserAndProxyAsync(HttpContext context, String targetUrl, Int32 remoteDebuggingPort, String messagePrefix, ILoggerFactory loggerFactory, CancellationTokenSource cts, Int32 browserReadyTimeoutMs) in /_/src/mono/wasm/debugger/DebuggerTestSuite/ChromeProvider.cs:line 56
   at DebuggerTests.TestHarnessStartup.<>c__DisplayClass13_0.<<Configure>b__1>d.MoveNext() in /_/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessStartup.cs:line 133 }
[xUnit.net 00:52:08.74]     DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange(variableName: "b", originalValue: 2, newValue: -500, overflowValue: 32769) [FAIL]
  Failed DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange(variableName: "b", originalValue: 2, newValue: -500, overflowValue: 32769) [1 ms]
  Error Message:
   System.IO.IOException : [testId: 650] Timed out after 20s waiting for the browser to be ready: C:\helix\work\correlation\chrome-win\chrome.exe
  Stack Trace:
     at DebuggerTests.WasmHostProvider.LaunchHostAsync(ProcessStartInfo psi, HttpContext context, Func`2 checkBrowserReady, String messagePrefix, Int32 hostReadyTimeoutMs, CancellationToken token) in /_/src/mono/wasm/debugger/DebuggerTestSuite/WasmHostProvider.cs:line 91
   at DebuggerTests.ChromeProvider.StartBrowserAndProxyAsync(HttpContext context, String targetUrl, Int32 remoteDebuggingPort, String messagePrefix, ILoggerFactory loggerFactory, CancellationTokenSource cts, Int32 browserReadyTimeoutMs) in /_/src/mono/wasm/debugger/DebuggerTestSuite/ChromeProvider.cs:line 56
   at DebuggerTests.TestHarnessStartup.<>c__DisplayClass13_0.<<Configure>b__1>d.MoveNext() in /_/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessStartup.cs:line 133
--- End of stack trace from previous location ---
   at DebuggerTests.Inspector.OpenSessionAsync(Func`3 getInitCmds, TimeSpan span) in /_/src/mono/wasm/debugger/DebuggerTestSuite/Inspector.cs:line 375
   at DebuggerTests.DebuggerTestBase.InitializeAsync() in /_/src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestBase.cs:line 149
[Result: IsOk: True, IsErr: False, Value: {
  "breakpointId": "1:539:8:dotnet://debugger-test.dll//_/src/mono/wasm/debugger/tests/debugger-test/debugger-test.cs",
  "locations": [
    {
      "scriptId": "dotnet://27277_1",
      "lineNumber": 542,
      "columnNumber": 8
    }
  ]
}, Error:  ]
[Result: IsOk: True, IsErr: False, Value: {
  "breakpointId": "1:1272:8:dotnet://debugger-test.dll//_/src/mono/wasm/debugger/tests/debugger-test/debugger-test.cs",
  "locations": []
}, Error:  ]
Results File: C:\helix\work\workitem\uploads\xharness-output\logs\testResults.trx

Failed!  - Failed:     1, Passed:   735, Skipped:     0, Total:   736, Duration: 57 m 43 s - DebuggerTestSuite.dll (net7.0)

C:\helix\work\workitem\e>set EXIT_CODE=1 
----- end Fri 09/30/2022 22:25:26.35 ----- exit code 1 ----------------------------------------------------------

{ 
    "ErrorMessage":"Timed out after 20s waiting for the browser to be ready",
    "BuildRetry": true
}

Report

Build	Definition	Test	Pull Request
89874	dotnet/runtime	chrome-DebuggerTests.CallFunctionOnTests.WorkItemExecution	#78651
84496	dotnet/runtime	chrome-DebuggerTests.PointerTests.WorkItemExecution	#77130
81128	dotnet/runtime	chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution	#76500
74554	dotnet/runtime	chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution
73865	dotnet/runtime	chrome-DebuggerTests.SetVariableValueTests.WorkItemExecution	#77521
70468	dotnet/runtime	chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution	#77594
69054	dotnet/runtime	chrome-DebuggerTests.SetVariableValueTests.WorkItemExecution	#76477
66413	dotnet/runtime	chrome-DebuggerTests.WorkItemExecution	#74820
60308	dotnet/runtime	chrome-DebuggerTests.WorkItemExecution	#77133

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
1	2	9

The text was updated successfully, but these errors were encountered:

ghost · 2022-10-03T10:02:26Z

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

Issue Details

Affected test:

DebuggerTests.SetVariableValueTests.DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange

Error: System.IO.IOException : [testId: 650] Timed out after 20s waiting for the browser to be ready: C:\helix\work\correlation\chrome-win\chrome.exe

Runfo failures in last 30 days as of 10/3:

Day	Run	Details
9/30	Rolling run 36814	net7.0-Browser-Release-wasm-Mono_chrome_Release-WasmDebuggerTests-(Windows.Amd64.Server2022.Open)windows.amd64.server2022.open
9/27	Rolling run 32310	net7.0-Browser-Release-wasm-Mono_chrome_Release-WasmDebuggerTests-(Windows.Amd64.Server2022.Open)windows.amd64.server2022.open

Error example from Console log:

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
OpenSession crashing. proxy state: RunLoopExitState { reason = Exception, exception = System.IO.IOException: [testId: 650] Timed out after 20s waiting for the browser to be ready: C:\helix\work\correlation\chrome-win\chrome.exe
   at DebuggerTests.WasmHostProvider.LaunchHostAsync(ProcessStartInfo psi, HttpContext context, Func`2 checkBrowserReady, String messagePrefix, Int32 hostReadyTimeoutMs, CancellationToken token) in /_/src/mono/wasm/debugger/DebuggerTestSuite/WasmHostProvider.cs:line 91
   at DebuggerTests.ChromeProvider.StartBrowserAndProxyAsync(HttpContext context, String targetUrl, Int32 remoteDebuggingPort, String messagePrefix, ILoggerFactory loggerFactory, CancellationTokenSource cts, Int32 browserReadyTimeoutMs) in /_/src/mono/wasm/debugger/DebuggerTestSuite/ChromeProvider.cs:line 56
   at DebuggerTests.TestHarnessStartup.<>c__DisplayClass13_0.<<Configure>b__1>d.MoveNext() in /_/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessStartup.cs:line 133 }
[xUnit.net 00:52:08.74]     DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange(variableName: "b", originalValue: 2, newValue: -500, overflowValue: 32769) [FAIL]
  Failed DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange(variableName: "b", originalValue: 2, newValue: -500, overflowValue: 32769) [1 ms]
  Error Message:
   System.IO.IOException : [testId: 650] Timed out after 20s waiting for the browser to be ready: C:\helix\work\correlation\chrome-win\chrome.exe
  Stack Trace:
     at DebuggerTests.WasmHostProvider.LaunchHostAsync(ProcessStartInfo psi, HttpContext context, Func`2 checkBrowserReady, String messagePrefix, Int32 hostReadyTimeoutMs, CancellationToken token) in /_/src/mono/wasm/debugger/DebuggerTestSuite/WasmHostProvider.cs:line 91
   at DebuggerTests.ChromeProvider.StartBrowserAndProxyAsync(HttpContext context, String targetUrl, Int32 remoteDebuggingPort, String messagePrefix, ILoggerFactory loggerFactory, CancellationTokenSource cts, Int32 browserReadyTimeoutMs) in /_/src/mono/wasm/debugger/DebuggerTestSuite/ChromeProvider.cs:line 56
   at DebuggerTests.TestHarnessStartup.<>c__DisplayClass13_0.<<Configure>b__1>d.MoveNext() in /_/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessStartup.cs:line 133
--- End of stack trace from previous location ---
   at DebuggerTests.Inspector.OpenSessionAsync(Func`3 getInitCmds, TimeSpan span) in /_/src/mono/wasm/debugger/DebuggerTestSuite/Inspector.cs:line 375
   at DebuggerTests.DebuggerTestBase.InitializeAsync() in /_/src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestBase.cs:line 149
[Result: IsOk: True, IsErr: False, Value: {
  "breakpointId": "1:539:8:dotnet://debugger-test.dll//_/src/mono/wasm/debugger/tests/debugger-test/debugger-test.cs",
  "locations": [
    {
      "scriptId": "dotnet://27277_1",
      "lineNumber": 542,
      "columnNumber": 8
    }
  ]
}, Error:  ]
[Result: IsOk: True, IsErr: False, Value: {
  "breakpointId": "1:1272:8:dotnet://debugger-test.dll//_/src/mono/wasm/debugger/tests/debugger-test/debugger-test.cs",
  "locations": []
}, Error:  ]
Results File: C:\helix\work\workitem\uploads\xharness-output\logs\testResults.trx

Failed!  - Failed:     1, Passed:   735, Skipped:     0, Total:   736, Duration: 57 m 43 s - DebuggerTestSuite.dll (net7.0)

C:\helix\work\workitem\e>set EXIT_CODE=1 
----- end Fri 09/30/2022 22:25:26.35 ----- exit code 1 ----------------------------------------------------------

Author:	karelz
Assignees:	-
Labels:	`arch-wasm`, `area-Debugger-mono`
Milestone:	-

.. they failed while waiting for the browser to launch. Related: https://github.com/dotnet/arcade/tree/main/src/Microsoft.DotNet.Helix/Sdk#test-retry Fixes dotnet#76528

….. (#78357) .. they failed while waiting for the browser to launch. Related: https://github.com/dotnet/arcade/tree/main/src/Microsoft.DotNet.Helix/Sdk#test-retry Fixes #76528

radical · 2022-11-21T08:49:13Z

Re-opening because #78357 didn't work. I will test in a new PR.

karelz added arch-wasm WebAssembly architecture area-Debugger-mono labels Oct 3, 2022

ghost added the untriaged New issue has not been triaged by the area owner label Oct 3, 2022

radical removed the untriaged New issue has not been triaged by the area owner label Oct 3, 2022

radical self-assigned this Oct 3, 2022

radical added the Known Build Error Use this to report build issues in the .NET Helix tab label Oct 4, 2022

radical changed the title ~~DebuggerTests.SetVariableValueTests.DebuggerTests.SetVariableValueTests.SetLocalPrimitiveTypeVariableOutOfRange - Browser not ready~~ [was Oct 7, 2022

radical changed the title ~~[was~~ [wasm] add support for retrying debugger tests when chrome launch times out Oct 7, 2022

lewing mentioned this issue Oct 8, 2022

Chrome debugger tests timeout #76750

Closed

radical mentioned this issue Nov 15, 2022

[wasm] Use Helix's retry mechanism to re-run debugger tests on CI if .. #78357

Merged

ghost added the in-pr There is an active PR which will close this issue when it is merged label Nov 15, 2022

radical mentioned this issue Nov 15, 2022

[wasm][debugger][tests] Retry when we fail to get the connection string from chrome #64931

Closed

radical closed this as completed in #78357 Nov 16, 2022

ghost removed the in-pr There is an active PR which will close this issue when it is merged label Nov 16, 2022

radical reopened this Nov 21, 2022

ghost added the untriaged New issue has not been triaged by the area owner label Nov 21, 2022

This was referenced Nov 21, 2022

Chrome Debugger Tests timeout #78599

Closed

[wasm] Update failure message for helix retry #78655

Merged

ghost added the in-pr There is an active PR which will close this issue when it is merged label Nov 21, 2022

radical closed this as completed in #78655 Nov 21, 2022

ghost removed in-pr There is an active PR which will close this issue when it is merged untriaged New issue has not been triaged by the area owner labels Nov 21, 2022

radical removed the Known Build Error Use this to report build issues in the .NET Helix tab label Nov 21, 2022

ghost locked as resolved and limited conversation to collaborators Dec 22, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[wasm] add support for retrying debugger tests when chrome launch times out #76528

[wasm] add support for retrying debugger tests when chrome launch times out #76528

karelz commented Oct 3, 2022 •

edited by build-analysis bot

Loading

ghost commented Oct 3, 2022

radical commented Nov 21, 2022

[wasm] add support for retrying debugger tests when chrome launch times out #76528

[wasm] add support for retrying debugger tests when chrome launch times out #76528

Comments

karelz commented Oct 3, 2022 • edited by build-analysis bot Loading

Report

Summary

ghost commented Oct 3, 2022

radical commented Nov 21, 2022

karelz commented Oct 3, 2022 •

edited by build-analysis bot

Loading