Steven Weerdenburg

I can't really explain _why_ it happens, but this feels related to the changes in the `Timeout` attribute. This setting gets read in here: https://github.com/nunit/nunit/blob/331944e9ff422beefd7f6b69266b707b42df4480/src/NUnitFramework/framework/Api/NUnitTestAssemblyRunner.cs#L312-L313 Which I think then causes...

@patrykpiotrmarek Sorry it took us a while to investigate. This means that at least as a workaround it should be possible to see the output on .NET 8 by applying...

Good point, thanks @manfred-brands ! I had forgotten to mention that. It's also worth mentioning that `CancelAfter` is a better alternative to `Timeout` on newer runtimes like NET8 in particular...

A bit of an update here as I have to pause my own investigation for now An early option I'd considered but had to rule out was passing the TextWriter...

Fantastic, thanks @manfred-brands . I took a quick look through your Timeout PR and it looks like it's taking things in a great direction

@SeanKilleen I don't know if I'd have the time to help with this myself, but would you be open to if someone were to help get this back in sync...

@CharliePoole @rprouse https://github.com/nunit/nunit/issues/3719 has gotten some traction recently. Based on Charlie's latest comments in this issue, he suggested: > Somebody would have to design an approach and somebody would have...

Welcome @PapisKang ! We would very much appreciate your help and contribution with your proposed changes. Would you be interested in opening PRs? As a new contributor, please feel free...

@OsirisTerje I spun this out as a separate issue for discussion from your point in https://github.com/nunit/nunit/issues/3325#issuecomment-1515219638 so that it doesn't get buried in the other things there. I'm also curious...

FWIW I like the analyzer approach, but I wonder if using them as a "migration path" here would then necessitate distributing them within the framework. I think we've already been...