You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Source or binary build?
From source, humble (13e5592)
Description
Expected behavior: ros_gz packages should build successfully
Actual behavior: Failed <<< ros_gz_sim [0.42s, exited with code 2]
I noticed this today when the build for one of our docker images failed.
I could reproduce the problem on 2 separate machines (in docker).
It was working before I ran apt upgrade and not working after the following packages were upgraded:
We first saw a build failure in a clean docker build (only saw the that the package failed to build, not why) and reproduced it in an old build using apt upgrade and colcon build. Can try again with a clean build tomorrow.
Doing a clean colcon build fixed the issue in the old docker builds. A clean docker build also seems to work today.
Still don't know why it failed yesterday though... Do you have any theories?
Doing a clean colcon build fixed the issue in the old docker builds. A clean docker build also seems to work today. Still don't know why it failed yesterday though... Do you have any theories?
Good to hear it's working. I have no idea why it would have failed yesterday. The 7.4.0 release was made on March 15.
I'll go ahead and close this issue since it doesn't appear to be a bug in ros_gz
Environment
From source, humble (13e5592)
Description
Failed <<< ros_gz_sim [0.42s, exited with code 2]
I noticed this today when the build for one of our docker images failed.
I could reproduce the problem on 2 separate machines (in docker).
It was working before I ran apt upgrade and not working after the following packages were upgraded:
I suspect that a new release of
libgz-math7
could be the cause, but have not verified this.Steps to reproduce
apt update
apt upgrade
colcon build --merge-install
Output
The text was updated successfully, but these errors were encountered: