Disable fail-fast in workflow matrix strategy so all configs get tested#1048
Merged
Disable fail-fast in workflow matrix strategy so all configs get tested#1048
Conversation
…ed even if some fail
jfy133
changed the title
maxulysse
approved these changes
Mar 19, 2026
Member
|
I think we do need that for now indeed |
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
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.
I noticed that for people trying to update to strict syntax, that it is annoying that you cannot see if your config now pass linting, just because someone else's config fails.
This sets
fail-fastto false, as our tests are technically independent from each other.