-
Notifications
You must be signed in to change notification settings - Fork 23
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Issue Description
The Docker CD pipeline fails when attempting to build the project. The build fails specifically when attempting to build and install blue_control.
Steps to Reproduce
The job under investigation is here. The behavior can be reproduced by re-running the build pipeline.
Expected Behavior
There should be no issues building the full Docker pipeline.
Error Message
#33 1.534 Starting >>> ros_gz_interfaces
#33 1.547 Starting >>> ros_gz_sim
#33 26.68 --- stderr: ros_gz_sim
#33 26.68 CMake Warning at /usr/share/cmake/gz-cmake3/cmake3/GzFindPackage.cmake:155 (message):
#33 26.68 ign_find_package is deprecated, use gz_find_package instead.
#33 26.68 Call Stack (most recent call first):
#33 26.68 CMakeLists.txt:41 (ign_find_package)
#33 26.68
#33 26.68
#33 26.68 ---
#33 26.68 Finished <<< ros_gz_sim [25.1s]
#33 26.68 Starting >>> blue_bringup
#33 28.54 --- stderr: blue_bringup
#33 28.54 CMake Warning:
#33 28.54 Manually-specified variables were not used by the project:
#33 28.54
#33 28.54 CMAKE_EXPORT_COMPILE_COMMANDS
#33 28.54
#33 28.54
#33 28.54 ---
#33 28.54 Finished <<< blue_bringup [1.86s]
#33 28.55 Starting >>> blue_control
#33 30.19 --- stderr: blue_control
#33 30.19 CMake Error at CMakeLists.txt:35 (find_package):
#33 30.19 By not providing "Findblue_dynamics.cmake" in CMAKE_MODULE_PATH this
#33 30.19 project has asked CMake to find a package configuration file provided by
#33 30.19 "blue_dynamics", but CMake did not find one.
#33 30.19
#33 30.19 Could not find a package configuration file provided by "blue_dynamics"
#33 30.19 with any of the following names:
#33 30.19
#33 30.19 blue_dynamicsConfig.cmake
#33 30.19 blue_dynamics-config.cmake
#33 30.19
#33 30.19 Add the installation prefix of "blue_dynamics" to CMAKE_PREFIX_PATH or set
#33 30.19 "blue_dynamics_DIR" to a directory containing one of the above files. If
#33 30.19 "blue_dynamics" provides a separate development package or SDK, be sure it
#33 30.19 has been installed.
#33 30.19
#33 30.19
#33 30.19 ---
#33 30.19 Failed <<< blue_control [1.64s, exited with code 1]
#33 77.43 Aborted <<< ros_gz_interfaces [1min 16s]
#33 77.46
#33 77.46 Summary: 2 packages finished [1min 16s]
#33 77.46 1 package failed: blue_control
#33 77.46 1 package aborted: ros_gz_interfaces
#33 77.46 3 packages had stderr output: blue_bringup blue_control ros_gz_sim
#33 77.46 7 packages not processed
#33 ERROR: executor failed running [/bin/sh -c . "/opt/ros/${ROS_DISTRO}/setup.sh" && colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON --ament-cmake-args -DCMAKE_BUILD_TYPE=Release --event-handlers desktop_notification- status- && sed -i "s#/opt/ros/\$ROS_DISTRO/setup.bash#$ROS_UNDERLAY/setup.sh#g" /ros_entrypoint.sh]: exit code: 1Runtime Environment
The Docker CI pipeline
Additional Context
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working