Skip to content
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

Do not fail the deep test check on in progress runs #3363

Merged
merged 5 commits into from
Jan 17, 2023

Conversation

keyboardDrummer
Copy link
Member

If there is a deep test check, and multiple runs qualify for that check, but the most recent run in still in progress, do not fail the check on that run, but instead look at the first not in progress run.

Also add a missing return statement so we don't get don't confusing error reporting like this:
image

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

@fabiomadge
Copy link
Collaborator

fabiomadge commented Jan 14, 2023

Doesn't this mean that the tests always run as long as there is a deep test in progress? You should still make sure that the previous run passed.

@keyboardDrummer
Copy link
Member Author

Doesn't this mean that the tests always run as long as there is a deep test in progress? You should still make sure that the previous run passed.

You're right, thanks! Updated the code.

fabiomadge
fabiomadge previously approved these changes Jan 16, 2023
core.setFailed(`Last run of ${runFilterDesc} did not succeed: ${run.html_url}`)
return
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you pull that out?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will, but I wonder whether it's worth the extra build trip ^,^

@keyboardDrummer keyboardDrummer enabled auto-merge (squash) January 17, 2023 10:15
@keyboardDrummer keyboardDrummer merged commit a75e209 into dafny-lang:master Jan 17, 2023
@keyboardDrummer keyboardDrummer deleted the fixDeepCheck branch January 17, 2023 14:54
davidcok pushed a commit to davidcok/dafny that referenced this pull request Jan 18, 2023
If there is a deep test check, and multiple runs qualify for that check,
but the most recent run in still in progress, do not fail the check on
that run, but instead look at the first not in progress run.

Also add a missing return statement so we don't get don't confusing
error reporting like this:
<img width="1011" alt="image"
src="https://user-images.githubusercontent.com/3121201/212307198-f0041b1c-e6dc-4852-ab75-38816122eeff.png">

<small>By submitting this pull request, I confirm that my contribution
is made under the terms of the [MIT
license](https://github.com/dafny-lang/dafny/blob/master/LICENSE.txt).</small>
davidcok pushed a commit to davidcok/dafny that referenced this pull request Jan 20, 2023
If there is a deep test check, and multiple runs qualify for that check,
but the most recent run in still in progress, do not fail the check on
that run, but instead look at the first not in progress run.

Also add a missing return statement so we don't get don't confusing
error reporting like this:
<img width="1011" alt="image"
src="https://user-images.githubusercontent.com/3121201/212307198-f0041b1c-e6dc-4852-ab75-38816122eeff.png">

<small>By submitting this pull request, I confirm that my contribution
is made under the terms of the [MIT
license](https://github.com/dafny-lang/dafny/blob/master/LICENSE.txt).</small>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants