ci(acceptance): do not cancel sibling suites on the first failure - #41767
Merged
Conversation
Each acceptance test workflow runs different test scenarios. If one acceptance test suite fails, we still want to see the results of the other test suites. Signed-off-by: Phillip Davis <phil@jankaritech.com>
DeepDiver1975
approved these changes
Jul 30, 2026
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.
Each acceptance test workflow runs different test scenarios. If one acceptance test suite fails, we still want to see the results of the other test suites.
This is similar to what was done in owncloud/reusable-workflows#90