-
Notifications
You must be signed in to change notification settings - Fork 353
Trigger shutdown transition in destructor (backport #1979) #2142
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
Conversation
Cherry-pick of b329679 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
f85b284
to
b5b4b57
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## humble #2142 +/- ##
==========================================
+ Coverage 63.55% 63.58% +0.02%
==========================================
Files 112 112
Lines 12821 12848 +27
Branches 8642 8660 +18
==========================================
+ Hits 8149 8169 +20
+ Misses 794 790 -4
- Partials 3878 3889 +11
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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.
Looks fine to me
Since ros2/rclcpp#2562 we get lots of warnings in the test logs like
I think we can just trigger the shutdown transition in the destructor of the base class.
We still had some warnings in tests of this repo when
rclcpp::shutdown()
is called before the node is destructed, and the context is invalid. The transition then would fail without therclcpp::ok()
check.This is an automatic backport of pull request #1979 done by Mergify.