Ask Your Question

Pre-release build failure to source for 3rd party package

asked 2014-07-11 04:49:31 -0500

samlcharreyron gravatar image

I've tried a pre-release test on the Hydro build farm for package libnabo. What I don't understand is that it is first build once succesfully, and then there is a second build that fails due to the following:

Retrieve the ROS build environment by sourcing /tmp/test_repositories/build_repository/install_isolated/ /!\ Failed to source /tmp/test_repositories/build_repository/install_isolated/ Failed to source /tmp/test_repositories/build_repository/install_isolated/

I cannot link to the log but you should be able to see it on Jenkins under prerelease-hydro-libnabo


edit retag flag offensive close merge delete


Got same issue on mavlink package.

vooon gravatar image vooon  ( 2014-07-13 06:46:44 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2014-07-14 12:19:13 -0500

Dirk Thomas gravatar image

updated 2014-07-15 14:30:34 -0500

The prereleases are not designed for packages with build type "cmake". Since they don't provide a common way for setting up the environment the buildfarm can't handle them.

Update: since the specific case was working before I will look into why it stopped working.

Update 2: fixed by

edit flag offensive delete link more


Does that mean it's not possible to test or build catkin packages on the build farm which depend on these packages?

samlcharreyron gravatar image samlcharreyron  ( 2014-07-14 14:10:18 -0500 )edit

If you prerelease a set of repositories the dependencies will be installed from Debian packages. I don't see an issue with that scenario. I would assume it is only a problem if you prerelease packages which are of build type "cmake". If that is not the case please provide links to specific prerelease jobs so that it is clear what is actually being tested.

Dirk Thomas gravatar image Dirk Thomas  ( 2014-07-14 14:33:58 -0500 )edit

Do you suggest that cmake-style packages should be removed from the prereleases then? E.g. the "octomap" repo started to fail only recently but was working before. If that's as intended then it should be communicated somewhere, e.g. by refusing "cmake" jobs outright.

AHornung gravatar image AHornung  ( 2014-07-15 04:01:51 -0500 )edit

Actually, it was the devel job that started failing recently:

AHornung gravatar image AHornung  ( 2014-07-15 04:04:42 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2014-07-11 04:49:31 -0500

Seen: 226 times

Last updated: Jul 15 '14