Spin before checking if ros time is active #483
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for a possible cause of a test failure described by this comment.
During the test the
ros_clock->ros_time_is_active()
method is expected to return false, but sometimes it returns true. "Ros Time" on a clock is activated or deactivated in a subscription callback on theparameter_events
topic. ASyncParametersClient
callsspin_node_until_future_complete
with anstd::shared_future
that completes when a response to a request to set parameters has been received. It looks like it is possible for the client response to be received before theparameter_events
subscription callback is called.Without this PR I see a test failure on my ubuntu xenial machine ~50% of the time using
--retest-until-fail 100
. With this PR--retest-until-fail 1800
completed without failing.I don't know why the change in #478 made this test flaky.
CI (only test rclcpp since only code change is in a test)