parallel: add option to not revive upon clear termination #30
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
yasunariw
force-pushed
the
no-relaunch-0
branch
from
d67005e to
bfd0f55
Compare
|
please make revive a variant |
yasunariw
changed the title
|
updated PR description |
yasunariw
force-pushed
the
no-relaunch-0
branch
from
6bceb8e to
7562d2b
Compare
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.
The PR enriches the semantics of
Parallel.run_forks ~revivewith an option to only revive workers with non-zero exit status. Setting~revive:Alwayspreserves the original behavior of~revive:true.Success is naturally determined by the Unix exit status, so child processes now return 1 if they exit with an exception.
This is joint work with @yasunariw .