-
Notifications
You must be signed in to change notification settings - Fork 51
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
Call rclcpp::init and rclcpp::shutdown in each test for test_rclcpp #454
Conversation
Signed-off-by: Stephen Brawner <brawner@gmail.com>
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.
I've got some questions inline. Also, the Rpr job is unhappy for some reason.
29eda28
to
4770f4f
Compare
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.
Sorry about the messy second commit. I didn't fully vet the first commit before pushing because it was taking eons to run and test on windows.
Signed-off-by: Stephen Brawner <brawner@gmail.com>
I discovered that the Windows is unstable because of one cmake warning in fastcdr, but the tests otherwise pass. |
@Mergifyio backport foxy |
✅ Backports have been created
|
We're seeing many hangs on windows CI jobs in these tests, and I think the issue can be resolved by ensuring that
rclcpp::shutdown
gets called for each invocation ofrclcpp::init
. In the process of addressing this, I noticed that the test_remote_parameters wasn't setting up the test cases correctly for each rmw_implementation.There may be some uncrustify issues to cleanup.
Testing
--packages-select test_rclcpp
Signed-off-by: Stephen Brawner brawner@gmail.com