-
Notifications
You must be signed in to change notification settings - Fork 62
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
Making sure the MultiprocessingParallelManager cleans up when done #1211
Conversation
I am going to adjust the semantics of this to make it identical in behavior to the prior implementation. |
@watertap-org/parameter-sweep just testing team notifications for the newly created https://github.com/orgs/watertap-org/teams/parameter-sweep org team. |
This reverts commit 5354b17.
The timeout tests are run here: https://github.com/bknueven/watertap/actions/runs/6948646192?pr=17. c241426 takes a much different approach and doesn't change the core algorithm. But I think it does address the issue. |
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
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1211 +/- ##
==========================================
+ Coverage 91.21% 94.91% +3.70%
==========================================
Files 343 344 +1
Lines 34900 34919 +19
==========================================
+ Hits 31834 33144 +1310
+ Misses 3066 1775 -1291 ☔ View full report in Codecov by Sentry. |
…atertap-org/watertap#1211) * Try adding explicit timeout where possible/easy * Try one more timeout * Add quick n dirty way to shut down multiprocessing worker processes * Try using EAFP instead of checking Queue.empty() * Make timeout configurable with default value * Refactor to use logging * Reorder imports * remove timeout from concurrent.futures.wait * trying Pool implementation * Revert "trying Pool implementation" This reverts commit 5354b1794ae1195b1f9222f723e141908d7cfc76. * try using kill * pylint --------- Co-authored-by: Ludovico Bianchi <lbianchi@lbl.gov>
Fixes/Resolves: #1158
Summary/Motivation:
See #1158. This will call
kill
to clean up any hangingProcess
es at the end of the run using theMultiprocessingParallelManager
.Changes proposed in this PR:
Legal Acknowledgement
By contributing to this software project, I agree to the following terms and conditions for my contribution: