👷 Add "fail-fast: true" default strategy to build test CI #27215
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
Add
fail-fast: true
default strategy to build test CI so I don't have to look for this config option name/format when I want to make itfalse
😄Yes, CI tests can be run locally, but it takes ~1.5 hours on my machine to run through them all since they don't run in parallel like they do on GitHub.
Benefits
It'll be easier to toggle this option while running CI tests in a PR and narrow in on failing tests.