Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jkotas opened this issue Jun 15, 2024 · 5 comments
Open

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

jkotas opened this issue Jun 15, 2024 · 5 comments
Assignees
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono area-VM-threading-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@jkotas
Copy link
Member

jkotas commented Jun 15, 2024

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
1016432 dotnet/runtime WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
1015915 dotnet/runtime WasmTestOnChrome-ST-Wasm.Browser.EventPipe.Sample.WorkItemExecution #114643
1014017 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution #114576
1013976 dotnet/runtime WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution
1011733 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution #114473
1008185 dotnet/runtime WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
1006423 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution #114296
1002933 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution
1001527 dotnet/runtime WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
999375 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution
994633 dotnet/runtime WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution #113740
994559 dotnet/runtime WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
991329 dotnet/runtime WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
990850 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution #113822
984816 dotnet/runtime WasmTestOnFirefox-MT-System.Private.Xml.Tests.WorkItemExecution

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
2 5 15
@jkotas jkotas added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Jun 15, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jun 15, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jun 15, 2024
@jkotas jkotas added arch-wasm WebAssembly architecture area-VM-meta-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jun 15, 2024
@lewing
Copy link
Member

lewing commented Jun 18, 2024

#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
Copy link
Member

lewing commented Jun 18, 2024

Also lots of overlap with #102559

@lewing
Copy link
Member

lewing commented Jun 19, 2024

and #102955

@pavelsavara
Copy link
Member

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 pavelsavara changed the title Wasm test failure: Tests timed out. Killing driver service [browser][MT] test failure: Tests timed out. Killing driver service Aug 21, 2024
@pavelsavara
Copy link
Member

There is fail during MT sample app startup. Log

@pavelsavara pavelsavara added this to the Future milestone Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono area-VM-threading-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

No branches or pull requests

3 participants