-
Notifications
You must be signed in to change notification settings - Fork 914
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
Upstream compatibility #1119
Upstream compatibility #1119
Conversation
Compatibility for ros/genpy#79.
Due to scheduling / resource contention, `sleep`s and `wait_until`s may be delayed. The `SteadyTimerHelper` test class was not robust to these delays, which was likely the cause of a failing test (`multipleSteadyTimeCallbacks` in `timer_callbacks.cpp`:220).
f5f54d7
to
6cc95f9
Compare
a1527f3
to
04c43ed
Compare
04c43ed
to
03b16eb
Compare
} | ||
ROS_FATAL_STREAM("Done testing the message"); |
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 think the problem you are trying to identify here has been addressed by #1127.
@ros-pull-request-builder retest this please |
Thank you for the patch. It was very helpful in addressing the test failures.
|
@dirk-thomas Awesome, I couldn't track that one down. Thanks. |
I just ran the test executable in |
There are a number of upstream changes that broke tests. This PR aims to get lunar-devel passing tests again so PRs aren't failing.
sleep
s andwait_until
s may be delayed. TheSteadyTimerHelper
test class was not robust to these delays, which was likely the cause of a failing test in Avoids buffer overflow in xmlrpcpp if fd > 1024 #1113 (multipleSteadyTimeCallbacks in timer_callbacks.cpp:220), and forcing retests when Add SteadyTimer #1014 was being considered.