Skip to content

[wasm] WBT tests using BrowserRunner seem to hang on a subsequent dotnet new #97054

Closed

Description

@radical

WBT tests failing on #95980 . The pattern seems to be a test that uses BrowserRunner, then a subsequent test that uses ToolCommand (usually for dotnet new) gets stuck on waiting for the process to exit.

Notes from some investigation:

  • BrowserRunner uses ToolCommand to start a process for dotnet run, but never explicitly tries to close that.
  • this might be due to async completions not being able to post due to threadpools blocked?
  • There are a couple of Wait and task.Result calls which also block
  • Making the whole chain more async friendly, and killing the process in Dispose seems to help, but there is something still left

Note that these are being hit only on #95980, and not on main.

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Jan 16, 2024
  2. added a commit that references this issue on Jan 23, 2024
  3. self-assigned this
    on Jan 26, 2024
  4. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Jan 31, 2024
  5. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Feb 2, 2024
  6. ghost removed
    untriagedNew issue has not been triaged by the area owner
    on Feb 2, 2024
  7. locked and limited conversation to collaborators on Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions