Clean up when a job triggers an exception #395
Merged
Conversation
This file contains 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
msheakoski
changed the title
Fixes a condition that occurs when a running job triggers an uncaught exception. The job is left in a “running” state instead of “failed” and future jobs with the same name are not allowed to run.
ASKozienko
pushed a commit
that referenced
this pull request
Nov 2, 2018
Clean up when a job triggers an exception
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes a condition that occurs when a running job triggers an uncaught exception. The job is left in a “running” state instead of “failed” and future jobs with the same name are not allowed to run.
Fixes issue #385