Marco Rossignoli

> We are trying to analyse a test run that crashes / shutdown the agent. There is no way to diagnose what happened: You can enable crash dump extension https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-extensions-diagnostics#crash-dump...

Thanks @martincostello for reporting it, I'll check the length name issue, anyway I don't know if hang/crash works for native aot version. @brianrob @tommcdon we're using the environment variable for...

> The reason I found this bug in the the first place was I was specifically trying to diagnose a hang that is only happening to me in native AoT...

> The reason I found this bug in the the first place was I was specifically trying to diagnose a hang that is only happening to me in native AoT...

> What I'm unclear on is: how does the Microsoft.Testing.Extensions.HangDump system work? Does it invoke createdump directly? As reported here https://github.com/microsoft/testfx/issues/3097#issuecomment-2168650810 we use the env vars for the crash dump...

> That's exactly what I need. The blame-hang-timeout timeout is to guard against too long execution of a single test, but I don't want the actual dump which can be...

> Environment.FailFast will also trigger a dump if the system is setup to collect it, so that might not be ideal. Yep if the crash is setup, I prefer the...

Thanks for the feedback! > You should very strongly reconsider this constraint and just use the common abstractions instead. I can't stress this point enough. If there is anything else...