dotnet / dotnet/diagnostics

Running dotnet-trace with dotnet test as command hangs waiting for ResumeStartup

Open
#5,649 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
1.3k
Forks
404
Avg merge
2d 5h
Merged PRs (30d)
35

Description

When running a command such as `dotnet-trace collect --show-child-io -- dotnet test --no-restore --no-build` in a directory with a test project the following text is output and things seem to just hang:
```
Test run for C:\Path\To\TestProject.dll (.NETCoreApp,Version=v8.0)
The runtime has been configured to pause during startup and is awaiting a Diagnostics IPC ResumeStartup command from a Diagnostic Port.
DOTNET_DiagnosticPorts="dotnet-trace-18712-20251203_040310.socket,suspend,connect"
DOTNET_DefaultDiagnosticPortSuspend=0
```

I don't see any output stating the test project has started. Looking at the trace after terminating the process (CTRL+C) seems to output nothing meaningful and things like trx files, code coverage, file logs, etc. don't seem to be getting generated suggesting the `dotnet test` never executed.

Are there any docs outlining how to use this in the dotnet test scenario? Is there a task we're supposed to perform manually to force it to continue based on the log messages output above?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.