Youssef Victor
Youssef Victor
We should probably consider taking a breaking change and drop mono support.
Can you try passing `--no-progress`? @nohwnd I strongly think that when the terminal isn't capable of updating the progress in-place, we should really disable progress by default. I have been...
> I am not opposed to disabling the output in non-interactive scenarios Good. I think that's best. Please when you do so, make sure to fix that both on SDK...
@jkotas Are these createdump log controlled by `DOTNET_CreateDumpDiagnostics` and/or `DOTNET_CreateDumpVerboseDiagnostics`?
@bart-vmware The behavior difference locally vs CI could be due to different OS. Are you running on Unix in CI but Windows locally? For example, I see https://github.com/dotnet/runtime/blob/2f0cfc828cd997538ecb1b6111cbbb530f406d27/src/coreclr/debug/createdump/createdumpunix.cpp#L48 in the...
For the other part of the output, you see two exceptions with two stack traces. The first one is StackOverflow, and it's expected that we show this with stack trace....
Marking as feature request to control hangdump diagnostics then, and also we need to decide the default here.
> On macOS, the test runner doesn't log excessively, but it never completes, so no dump is uploaded. The GHA workflow is killed after 1 hour. This looks like another...
Updating the documentation in https://github.com/dotnet/docs/pull/50346
@bart-vmware Yes, this is xunit/xunit#3432. xunit decided to not address it so it's closed as not planned. The only workaround for you for xunit.v3 is the more complicated `codesign` workaround....