Don't run stage tagged "panic" on snippet #281
Merged
Conversation
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
Previously, the state was run, and the panic trapped. We are not making use of the information resulting from the panic. The simplest reasonable thing to do is not run stages tagged "panic". We leave this tag in place in order to say *why* we are skipping the stage. The idea is to fix these so that we can do a proper skip, and eventually, tag with ok.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously, the stage was run, and the panic trapped. We are not making use of the information resulting from the panic. The simplest reasonable thing to do is not run stages tagged "panic".
We keep this tag as an option in order to say why we are skipping the stage. The idea is to fix these so that we can do a proper skip, and eventually, tag with ok.