Re-raise error in rescue block of slurm integration test#1902
Merged
cdunbar13 merged 1 commit intoOct 31, 2023
Merged
Conversation
nick-stroud
approved these changes
Oct 31, 2023
…ate failures to cloud build
316bfa8 to
775c930
Compare
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.
Noticed during today's daily tests that if an integration test fails (specifically things like
test-mounts.yml), the rescue block of theslurm-integration-test.ymlblocks the error from propagating to cloud build so we don't notice it.This PR creates an error and propagates it upward similar to how it is done during the rescue block of the setup portion of the integration test.