-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fix throwing errors from Executor.join_async()
#208
Conversation
Codecov ReportBase: 37.96% // Head: 38.55% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## branch-22.11 #208 +/- ##
================================================
+ Coverage 37.96% 38.55% +0.59%
================================================
Files 101 101
Lines 2439 2443 +4
Branches 1144 1145 +1
================================================
+ Hits 926 942 +16
+ Misses 716 694 -22
- Partials 797 807 +10
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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
@gpucibot merge |
This PR was some outstanding work that was a result of changes in the SRF PR: nv-morpheus/MRC#208. If an exception is detected, we can try to manually call stop on all stages to allow for better shutdown behavior. Included in this PR are fixes to remove `CMAKE_BUILD_RPATH_USE_ORIGIN` from the CMake file which breaks building SRF with Morpheus at the same time. This option is only needed during the CI build so it was added manually to the CI scripts. Authors: - Michael Demoret (https://github.com/mdemoret-nv) Approvers: - David Gardner (https://github.com/dagardner-nv) URL: #478
Exceptions from both python and C++ were getting printed to the log but not raised in python when using
Executor.join_async()
. This boils down to the fact thatfuture::wait()
was called instead offuture::get()
which actually rethrows the exception.Added some tests to check this functionality