You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've started to run into a extremely odd problem that causes dotnet test to hang during the build phase. It's been rock solid for months, and then suddenly it's hanging on our CI machines and dev machines. We thought it was related to the rollout of net9 and the latest version of VS, but we've ruled that out over here.
For now our workaround is to pass --no-build which seems to work.
The other thing we also noticed is that is seems to be related to disabling the terminal logger using --tl:off.
We need to disable terminal logger because we shell out to dotnet test on our CI machines, and it can't cope with the new terminal logger.
It happens across multiple apps so we can rule out our application code.
We've ruled out a bunch of things in the ticket above.
That really weird thing is if we don't turn off the terminal logger then dotnet test passes (on our dev machines).
It's almost like --tl:off causes the output to block/hang somewhere?
Is there more we can do to narrow down why/how it is hanging on the build phase.
We've also tried _MSBUILDTLENABLED=0, and MSBUILDTERMINALLOGGER=off.
Cheers,
Indy
The text was updated successfully, but these errors were encountered:
We've started to run into a extremely odd problem that causes
dotnet test
to hang during thebuild
phase. It's been rock solid for months, and then suddenly it's hanging on our CI machines and dev machines. We thought it was related to the rollout of net9 and the latest version of VS, but we've ruled that out over here.For now our workaround is to pass
--no-build
which seems to work.The other thing we also noticed is that is seems to be related to disabling the terminal logger using
--tl:off
.We need to disable terminal logger because we shell out to
dotnet test
on our CI machines, and it can't cope with the new terminal logger.It happens across multiple apps so we can rule out our application code.
We've ruled out a bunch of things in the ticket above.
That really weird thing is if we don't turn off the terminal logger then
dotnet test
passes (on our dev machines).It's almost like
--tl:off
causes the output to block/hang somewhere?Is there more we can do to narrow down why/how it is hanging on the build phase.
We've also tried
_MSBUILDTLENABLED=0
, andMSBUILDTERMINALLOGGER=off
.Cheers,
Indy
The text was updated successfully, but these errors were encountered: