Closed claraberendsen closed 11 months ago
Waiting https://github.com/gazebo-release/gz-msgs10-release/pull/3 to land before debugging
Occurred today again. See https://build.osrfoundation.org/job/gz-transport13-debbuilder/343. It seems to be happening only when it rans on drogon (focal), not on the normal agents.
This happens after the debs have been built while running autopkgtest
. I'm not familiar with this process.
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 44769 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
[33mautopkgtest [10:58:45]: test build: [-----------------------
[0mIn file included from /usr/lib/x86_64-linux-gnu/pkgconfig/../../..//include/gz/transport13/gz/transport/Discovery.hh:71,
from /usr/lib/x86_64-linux-gnu/pkgconfig/../../..//include/gz/transport13/gz/transport.hh:26,
from gztest.cc:1:
/usr/lib/x86_64-linux-gnu/pkgconfig/../../..//include/gz/msgs10/gz/msgs/Utility.hh:24:10: fatal error: gz/math/AxisAlignedBox.hh: No such file or directory
24 | #include <gz/math/AxisAlignedBox.hh>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
[33mautopkgtest [10:58:45]: test build: -----------------------]
[0m[33mautopkgtest [10:58:45]: test build: - - - - - - - - - - results - - - - - - - - - -
[0mbuild FAIL non-zero exit status 1
[33mautopkgtest [10:58:46]: test build: - - - - - - - - - - stderr - - - - - - - - - -
[0mIn file included from /usr/lib/x86_64-linux-gnu/pkgconfig/../../..//include/gz/transport13/gz/transport/Discovery.hh:71,
from /usr/lib/x86_64-linux-gnu/pkgconfig/../../..//include/gz/transport13/gz/transport.hh:26,
from gztest.cc:1:
/usr/lib/x86_64-linux-gnu/pkgconfig/../../..//include/gz/msgs10/gz/msgs/Utility.hh:24:10: fatal error: gz/math/AxisAlignedBox.hh: No such file or directory
24 | #include <gz/math/AxisAlignedBox.hh>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
[33mautopkgtest [10:58:46]: @@@@@@@@@@@@@@@@@@@@ summary
[0mbuild FAIL non-zero exit status 1
[33mautopkgtest [10:58:46]: Binaries: resetting testbed apt configuration
[0mHit:1 http://packages.osrfoundation.org/gazebo/ubuntu-nightly jammy InRelease
Hit:2 http://packages.osrfoundation.org/gazebo/ubuntu-stable jammy InRelease
Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists...
W: http://packages.osrfoundation.org/gazebo/ubuntu-nightly/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://packages.osrfoundation.org/gazebo/ubuntu-stable/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
+ testret=4
+ [[ 4 != 0 ]]
+ [[ 4 != 8 ]]
+ echo 'Problem in running autopkgtest: $testret'
Problem in running autopkgtest: $testret
+ exit 1
Potential fix in https://github.com/gazebosim/gz-cmake/pull/374
Environment
Description
Seems this error has occurred before since build #284 and it seems it has the behavior where it would fail and on the next build pass. Could not determine what introduced this, it could possibly be something related to the build of gz-msgs10?
Output