-
Notifications
You must be signed in to change notification settings - Fork 514
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
CI is broken on Rolling #1970
Comments
|
Locally, I can build moveit_msgs against ros2-testing debs (and I uninstalled all of ros-rolling-* before tasting, so it's not a missing dependency). None of the service_msgs stuff is in the main ros2 repos (we haven't haven't had a sync yet) |
This commit could be the culprit: ros2/rosidl_defaults@a3f753d. But it still does not explain why service_msgs is not installed 🤔 |
To install missing ros-rolling-service-msgs. Closes: moveit#1970
The job uses an old Docker image of the ros2-testing repos where ros-rolling-service-msgs is not installed and it does not Edit: A third option would be to not install (old) packages in the base image. |
@tylerjw - I think this may be more up your alley - since it looks like it is our CI, not some upstream break |
Discussed this in the standup, the problem is that the ci-testing Docker images are based on the ci images which the added ros2-testing apt sources: https://github.com/ros-planning/moveit2/blob/main/.docker/ci-testing/Dockerfile and the |
I think we only need to add a rosdep step to ci-testing and that should be sufficient. The dependency in question (service_msgs) is not being installed in apt update / apt upgrade, it should be installed and triggered through |
@vatanaksoytezer no, service_msgs is a dependency of rcl already. |
The fix is almost certainly needed to be upstream - just ticketing here for visibility (so we don't have multiple people working on it)
It looks like the failure is actually in sensor_msgs:
The text was updated successfully, but these errors were encountered: