Add new option "fail-zero" #4716
Merged
Conversation
This file contains hidden or 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
110ffcc to
0460209
Compare
0460209 to
13d8bda
Compare
outsideris
approved these changes
Aug 14, 2021
13d8bda to
c611faa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
We add a new option
--fail-zerowhich exits the test script withexit-code: 1when no test have been found. Currently theexit-codewould be zero. This flag is especially useful for CI/CD environments to prevent bugs remaining undetected.Description of the Change
New option
fail-zero:Before an
EVENT_RUN_ENDevent is emitted, we setrunner.failures = 1. That way the script exits withexit-code: 1Applicable issues
closes #4062