-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy dump file to the Helix upload location #45345
Conversation
… hang but don't fail for expected longer tests
/backport to release/9.0.2xx |
Started backporting to release/9.0.2xx: /~https://github.com/dotnet/sdk/actions/runs/12242906180 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Were you able to verify that the dump files are available with this change?
Don't forget to change the timeout back to 30 minutes (unless you want to leave it at 15 minutes).
Bah, it didn't timeout. Trying again |
/azp run dotnet-sdk-public-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
@Evangelink this time it copied the test log over and there was a timeout. The log is huge though so not sure what I'm looking for. I'm also going to rerun again as this didn't even time out on arm64 like all the other runs. |
/azp run dotnet-sdk-public-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
https://dev.azure.com/dnceng-public/public/_build/results?buildId=896954&view=results <-- timeout on full framework |
This initial draft is meant to force hang dumps by setting the timeout arbitrarily low and then using PowerShell to determine where the saved .dmp file is so we know where to copy it from.