[browser][MT] test failure: Tests timed out. Killing driver service

[jkotas]

Build Information

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

Error Message

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

{
  "ErrorMessage": "Tests timed out. Killing driver service",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=732547
Error message validated: [Tests timed out. Killing driver service]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 7/8/2024 11:10:25 PM UTC

Report

Build	Definition	Test	Pull Request
1056275	dotnet/runtime	WasmTestOnChrome-ST-System.Drawing.Primitives.Tests.WorkItemExecution	#116070
1054457	dotnet/runtime	WasmTestOnChrome-ST-System.Linq.Queryable.Tests.WorkItemExecution	#116070
1053099	dotnet/runtime	WasmTestOnChrome-ST-System.Composition.Runtime.Tests.WorkItemExecution	#116070
1050842	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution	#115984
1049202	dotnet/runtime	WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
1045531	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution
1043619	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution	#115635
1043376	dotnet/runtime	WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution	#115576
1042913	dotnet/runtime	WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution	#115576
1041906	dotnet/runtime	WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution	#115544
1041490	dotnet/runtime	WasmTestOnChrome-ST-System.Threading.RateLimiting.Tests.WorkItemExecution	#115408
1041343	dotnet/runtime	WasmTestOnChrome-ST-System.Runtime.Tests.WorkItemExecution	#115408
1041032	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution	#115544
1040612	dotnet/runtime	WasmTestOnChrome-ST-System.Runtime.Tests.WorkItemExecution	#115408
1040229	dotnet/runtime	WasmTestOnChrome-ST-System.Threading.Tasks.Tests.WorkItemExecution	#115408
1039973	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution
1037430	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution
1035975	dotnet/runtime	WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution
1034320	dotnet/runtime	WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution	#115085

Summary

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

[lewing]

#102664 should be catching most of these but there are a couple that probably aren't matched by that or one of the other issues

[lewing]

Also lots of overlap with #102559

[lewing]

and #102955

[pavelsavara]

I think there is deadlock or something similar in emscripten's VFS.
It's running on UI thread only and I/O from all other threads needs to be dispatched there.

[pavelsavara]

There is fail during MT sample app startup. Log