-
Notifications
You must be signed in to change notification settings - Fork 435
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
Change behavior of timer on construction #146
Conversation
I'm working on getting #140 merged today, can we defer this fix until then? |
+1 |
Sure. I'll run tests with this branch to check its correctness but I won't On Thu, Nov 5, 2015 at 2:09 PM, William Woodall notifications@github.com
|
It looks good to me too. |
+1 |
1 similar comment
+1 |
0f23a16
to
dcd5117
Compare
Change behavior of timer on construction
This appears to have caused a regression in test_rclcpp: http://ci.ros2.org/job/ros2_batch_ci_linux/567/testReport/ I'll follow up with a fix. |
Signed-off-by: Mikael Arguedas <mikael.arguedas@gmail.com>
* add logs and minor fixes Signed-off-by: Alberto Soragna <alberto.soragna@gmail.com> * use >0 rather than ==1 in comparison Signed-off-by: Alberto Soragna <alberto.soragna@gmail.com> --------- Signed-off-by: Alberto Soragna <alberto.soragna@gmail.com>
* add logs and minor fixes Signed-off-by: Alberto Soragna <alberto.soragna@gmail.com> * use >0 rather than ==1 in comparison Signed-off-by: Alberto Soragna <alberto.soragna@gmail.com> --------- Signed-off-by: Alberto Soragna <alberto.soragna@gmail.com>
Fixes ros2/system_tests#36
Based on the discussion in ros2/system_tests#66
Previously, timers would fire on the very first call to spin, no matter how much time passed between their construction and the call to spin.
This PR will change the behavior of timers so that the timer will fire one period after being created, or on the first call to spin IF that call happens after one period.