Make gradle fail fast when running tests #2759
Open
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
To make Gradle fail fast when running tests, you can add the
--fail-fast
option to the test execution commands. This will ensure that the Gradle test tasks will stop as soon as any test fails.Motivation and Context
This is beneficial so that if there is a test that fails it does not keep executing all the rest of the tests. This will save time and resources since it will reach to a failed result faster. It takes around 12 minutes to run the tests, this way we do not need to wait for the job to finish if it encounters one failed test.
How Has This Been Tested?
Types of changes
Checklist: