-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Publish test artifacts on timeout and not just failure #1561
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
Conversation
@dotnet-bot rebuild this PR please. |
There is a syntax error in the yaml template that is why there is no steps shown in the build:
|
Yes I am still working on it! But thanks for already taking a look at it. |
Now it should be ready for review! |
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.
LGTM. Timeout seems reasonable, if we start seeing phases timing out we could just bump it up.
Fixes #1556.
In this PR I add a condition so that we post test artifacts not just in case of failures, but also in case of timeouts, by using
not(succeeded())
condition.I also set the timeout limit for the running the tests to 40 min (this does not include the build time). Still working on the right syntax for the timeout setting.