-
Notifications
You must be signed in to change notification settings - Fork 531
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
Refactor Servo velocity bounds enforcement. Disable flaky unit tests. #428
Conversation
Codecov Report
@@ Coverage Diff @@
## main #428 +/- ##
==========================================
- Coverage 51.41% 49.29% -2.12%
==========================================
Files 223 218 -5
Lines 23343 22985 -358
==========================================
- Hits 12000 11328 -672
- Misses 11343 11657 +314
Continue to review full report at Codecov.
|
Seems folks at nav2 had a similar case of flaky tests (see ros-navigation/navigation2#584). They solved it with seperating the test with the others. In a related note this PR should solve the test failures related to servo_server not being opened. |
This also includes #352 |
@JafarAbdi @AndyZe @tylerjw can you guys review this? It seems to pass for some time with multi thread and sleeps added to tests. |
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 glanced through the changes and left a couple comments. Thank-you for working on this. I'll test this soon and give you a more detailed review.
moveit_ros/moveit_servo/test/launch/test_servo_collision.test.py
Outdated
Show resolved
Hide resolved
I think you should rename the PR because it's more than just porting the ROS1 PR now. Maybe something like:
|
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.
Generally looks great!
moveit_ros/moveit_servo/test/launch/servo_launch_test_common.py
Outdated
Show resolved
Hide resolved
moveit_ros/moveit_servo/test/launch/test_servo_collision.test.py
Outdated
Show resolved
Hide resolved
moveit_ros/moveit_servo/test/launch/test_servo_integration.test.py
Outdated
Show resolved
Hide resolved
moveit_ros/moveit_servo/test/launch/test_servo_pose_tracking.test.py
Outdated
Show resolved
Hide resolved
moveit_ros/moveit_servo/test/launch/test_servo_singularity.test.py
Outdated
Show resolved
Hide resolved
moveit_ros/planning_interface/test/launch/move_group_ompl_constraints.test.py
Outdated
Show resolved
Hide resolved
@vatanaksoytezer: a small comment on logistics: it would be OK to Pushing individual commits leads to the CI infrastructure starting jobs every time you push, and it also leads to everyone who Watches this repository receiving emails for every individual push as well. Over the past few days, I've received 48 notifications about this PR alone, which seems a bit excessive. |
@gavanderhoorn thanks for the heads up and sorry that you've received so many notifications. Although I am aware that I should not push that much, for this PR I was actually pushing on purpose to trigger actions and see if the flakiness on tests continue. I cannot reproduce the errors in my local machine and wanted to try as much as I can to see if it breaks with those changes. On your comment I could probably test this in my own Github repository before opening the PR (which I did for the first 15 or so commits), but I found out tests be still failing after I opened the PR here. Will try my best to not push that much again. |
of course if you're trying to debug the GHA cfg, that would be a different situation. It was more of a general comment though. The same happened in a few other PRs.
that seems like a good approach indeed. |
No worries, I will be more careful with my other PRs. Thanks for giving the heads up. |
733ee87
to
5cca59b
Compare
@AndyZe @tylerjw @JafarAbdi I am thinking about disabling the tests again since CI still seems to fail with the same errors after my additions. |
Yep, I guess that is what we have to do. |
@vatanaksoytezer can you go ahead and set the tests back as they were previously and we'll get this merged? |
@AndyZe I was waiting for today's meetup to confirm disabling tests with other people as well. Will squash and update this PR afterwards. |
I'm sorry I've been slow to respond on this. I'll look more closely at this tonight. |
Only remaining problem is: https://github.com/ros-planning/moveit2/runs/2547716859?check_suite_focus=true#step:7:7976 any ideas @tylerjw @AndyZe ? Every other test works fine and as expected. I would honestly prefer to just disable this and merge this PR and open up a new one to fix that issue. |
Disabling that one test sounds fine to me. I checked the yaml file and it seems fine. It passes locally, too. Net test coverage still improves by a lot. |
The error seems to persist (see https://github.com/ros-planning/moveit2/runs/2548539403) |
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.
Blocking until flaky tests are resolved
554bb82
to
606abc0
Compare
OK, we have tried very hard to fix CI. I'm at the point where we just disable the tests again. |
I think that's fair. Probably we will have to leave to another day. |
ac06ed2
to
ce84511
Compare
I'm merging this, CI is fixed by #470. |
Port of moveit/moveit#2471 and an attempt to fix flakiness (again). Overall this PR: