[wasm] timeout in System.Runtime.Tests

[lewing]

timeout in System.Runtime.Tests in #76090

https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76090-merge-f53f7162d92744a59d/WasmTestOnBrowser-System.Runtime.Tests/1/console.4f411128.log?helixlogtype=result

ChromeDriver was started successfully.
[22:18:02] info: Incoming arguments: --run WasmTestRunner.dll System.Runtime.Tests.dll -notrait category=AdditionalTimezoneChecks -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[22:18:02] info: Application arguments: --run WasmTestRunner.dll System.Runtime.Tests.dll -notrait category=AdditionalTimezoneChecks -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[22:18:02] info: browser: [main] Console websocket connected.
[22:18:38] info: Initializing.....
[22:18:38] info: Discovering: System.Runtime.Tests.dll (method display = ClassAndMethod, method display options = None)
[22:18:43] info: Discovered:  System.Runtime.Tests.dll (found 8917 of 9067 test cases)
[22:18:43] info: Using random seed for test cases: 2021412321
[22:18:43] info: Using random seed for collections: 2021412321
[22:18:43] info: Starting:    System.Runtime.Tests.dll

...
[EXECUTION TIMED OUT]
Exit Code:-3Executor timed out after 3600 seconds and was killed

['WasmTestOnBrowser-System.Runtime.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

[ghost]

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

Issue Details

---

timeout in System.Runtime.Tests in #76090

https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76090-merge-f53f7162d92744a59d/WasmTestOnBrowser-System.Runtime.Tests/1/console.4f411128.log?helixlogtype=result

ChromeDriver was started successfully.
[22:18:02] info: Incoming arguments: --run WasmTestRunner.dll System.Runtime.Tests.dll -notrait category=AdditionalTimezoneChecks -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[22:18:02] info: Application arguments: --run WasmTestRunner.dll System.Runtime.Tests.dll -notrait category=AdditionalTimezoneChecks -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[22:18:02] info: browser: [main] Console websocket connected.
[22:18:38] info: Initializing.....
[22:18:38] info: Discovering: System.Runtime.Tests.dll (method display = ClassAndMethod, method display options = None)
[22:18:43] info: Discovered:  System.Runtime.Tests.dll (found 8917 of 9067 test cases)
[22:18:43] info: Using random seed for test cases: 2021412321
[22:18:43] info: Using random seed for collections: 2021412321
[22:18:43] info: Starting:    System.Runtime.Tests.dll

...
[EXECUTION TIMED OUT]
Exit Code:-3Executor timed out after 3600 seconds and was killed

['WasmTestOnBrowser-System.Runtime.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

Author:	lewing
Assignees:	-
Labels:	arch-wasm, area-VM-meta-mono
Milestone:	-

[lewing]

@radekdoulik @maraf @radical looks like a hang on windows?

[radical]

I have seen a few of these on rolling builds.

[radical]

Another instance - build, and log on #76236 - release/7.0 branch.

[lewing]

have we seen this after we disabling the msbuild service?

[radical]

I haven't seen this recently on rolling builds.