Open AArnott opened 2 weeks ago
Tagging subscribers to this area: @tommcdon See info in area-owners.md if you want to be subscribed.
@AArnott do you know how the dumps are being collected? From the log it seems that the app is not suspended while createdump was launched, and by the time createdump attempted to collect a dump the process had already exited. Are the .NET crash dump environment variables set and if yes, do you know how they are configured?
I don't know how the dump is triggered. @nohwnd should know more. I just know that we request crash dumps when we spawn the test runner via dotnet test
and a dump is triggered (for a failure that I would expect and need a dump collected). As for the process continuing to execute during the dump collection and how to stop that, I hope @nohwnd can comment.
Yes, we set the variables here, then we wait for the process to finishe, and we grab any dump files that were collected. https://github.com/microsoft/vstest/blob/main/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/BlameCollector.cs#L157-L166
Thanks @nohwnd and @AArnott! This might be related to https://github.com/dotnet/runtime/issues/103000.
@mikem8361, assigning over to you for further investigation
Description
I have a particularly annoying bug that frequently crashes the test runner in Azure Pipelines but thus far hasn't repro'd locally on a dev box. I need a dump of the process to investigate, but no dump in produced.
Here is a sample crash.
In the cases I have, the crashes happen on linux. What additional steps must I take in my pipeline to get a dump collected?
.NET SDK 8.0.300 .NET 8.0.6
Reproduction Steps
The command that runs the test includes
--blame-crash
and other switches. On Windows agents I also acquireprocdump
and set thePROCDUMP_PATH
environment variable.Expected behavior
A dump file that Azure Pipelines artifacts can collect.
Actual behavior
The dump fails to be collected.
Regression?
Pretty sure, yes, since I have multiple times verified that dump collection works in the past. Probably the last time I verified this was on .NET 6.
Known Workarounds
No response
Configuration
No response
Other information
No response