-
Notifications
You must be signed in to change notification settings - Fork 43
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
[bug] failing build on rolling #254
Comments
Hi, @JanStaschulat, I like your idea of cloning the rmw repo in the CI action until it has been released. |
I'm also ok with cloning it |
But still I am wondering, why the most recent version of the |
cloning the repo did not solve the problem
https://github.com/ros2/rclc/runs/5372137665?check_suite_focus=true I am trying now to add |
unfortunately they have not increased the version of rmw package. It is still So the rmw packge with EventsExecutor PR has the same version as the released rolling package 3 months ago. :( |
cloning the repo in a seperate step (e.g. step before building rclc) did not resolve the error.
https://github.com/ros2/rclc/runs/5372614775?check_suite_focus=true |
tried several things, but none of them revolved the issue:
@wjwwood @christophebedard any suggestions?
|
This repo has
As I mentioned over on the PR, if you add |
@christophebedard thanks a lot for your suggestion. I added the relevant rmw repositories to The PR now builds successfully :) |
Created an issue to remove these dependencies, once these changes in rmw become available as ROS 2 rolling distribution. |
We don't necessarily do releases after every change, so building just rcl from master while using rmw and other packages from binary is only going to work sometimes, because that's a combination we just don't test and honestly isn't a very logical selection of versions to build together. I'd recommend with building all dependencies from source or building none from source, but that sounds like something you can configure in the Actions you're using. An rmw release should happen in a few days. |
@wjwwood Thank you very much for your feedback. |
CI job fails on rolling because of Events Executor PR (ros2/rmw#286) A new header file has been added to rmw repository, but the rmw package is not cloned in ros-tooling/actions-ros-ci :
ros-tooling/action-ros-ci
creates it's own docker container in which thercl
-package is built from scratch but not thermw
package:https://github.com/ros2/rclc/runs/5372614775?check_suite_focus=true
https://github.com/ros2/rclc/runs/5371188010?check_suite_focus=true
A new file (
event_callback_type.h
) has been added to the repository.We cannot
sudo apt-get install
the new rmw package, becausermw
has not been released as bloom release lately:https://github.com/ros/rosdistro/commits/master/rolling
@ralph-lange @pablogs9 Shall we clone the 'rmw' repo in the CI action for now, like here? Any other suggestions?
The text was updated successfully, but these errors were encountered: