keep running tests even if earlier ones failed #10361
Open
+8
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geekosaur
force-pushed
the
make-it-go
branch
from
e292f97
to
5779675
Compare
|
Aren't we going to saturate CI resources pretty fast this way? |
|
Yes, as I observed with #10291. But see #10263; @mpickering is insisting it's necessary. |
Matt Pickering says we should always run all tests. This uses `continue-on-error: true` to run them as long as the build succeeded.
geekosaur
force-pushed
the
make-it-go
branch
from
5779675
to
8617a7e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Matt Pickering says we should always run all tests. This uses
continue-on-error: trueto run them as long as the build succeeded.Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: