-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminate other processes if one breaks #75
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, as discussed offline: please add a test that catches this RuntimeError
and then checks if there are no processes still in multiprocess.active_children()
…r breaking the job
Not done yet, will let you know when ready ;) |
…ding output during unittesting
Okay, good to go for my part! I added in a stdout/stderr muting option for spawning processes during unit tests to prevent the terminal showing an error message during the tests. Let me know if you agree with how I did that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple implementation issues, looks good otherwise
…st_mute to make it explicit that this is purely for testing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last nitpick for the documentation, LGTM otherwise
Co-authored-by: Sander Roet <[email protected]>
Thanks for spotting! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, feel free to merge
Noticed a multiprocessing problem (unrelated to #74). When one of the processes fails, the other will keep running. This is undesired as the results will become unusable. Now I explicitly terminate all processes when one fails before raise a runtimeerror in the main process.
(I previsouly thought that 'raise RuntimeError' would be propagated to child processes, but that is apparently not the case)