[Ros-release] Wet Prereleases

Tully Foote tfoote at willowgarage.com
Fri Feb 15 21:03:19 UTC 2013

This is a regression in the old performance.  The issues is that when
testing several packages together, it pulls in the union of their system
dependencies, but when building the debs, they only get their own declared
ones.  We should make the prerelease capture each of their dependencies.  I
ticket at https://github.com/ros-infrastructure/jenkins_scripts would be a
good place to track this.

On Fri, Feb 15, 2013 at 12:58 PM, Thibault Kruse <kruset at in.tum.de> wrote:

>  Hi Daniel,
> and sorry all that I forgot to reply to the list,
> On 15.02.2013 14:13, Daniel Stonier wrote:
> On 15 February 2013 18:49, Thibault Kruse <kruset at in.tum.de> wrote:
>> Hi Daniel,
>> On 15.02.2013 02:51, Daniel Stonier wrote:
>>> These fails also happen in other ways - e.g. a missing
>>> find_package(catkin REQUIRED ...) in just one package in the stack also
>>> gets past pre-release.
>>  There is a script called catkin_make_isolated that people can use to
>> build packages in isolation. This can help detect certain missing declared
>> dependencies. So maintainers can make sure both catkin_make and
>> catkin_make_isolated pass locally before heading on to pre-release.
>  That's interesting - hadn't discovered that tool before. Just did a
> quick run, and while it would catch some issues, it would still not catch
> the install dependency problems I outlined in the first email (unless I
> manually sandboxed, cleared all the debs and reinstalled individual package
> dependencies inbetween each isolated build).
> Feel free to add a pointer to that script on the wiki where you would
> expect it.
> Indeed not all problems can be found that way, only some that would fall
> through a normal catkin workspace build.
> A more complete check tests for the following:
> 1.) Building a package together with a maximum amount of other package in
> the same workspace with tests to check for cmake namespace collisions.
> 2.) Build each package in isolation to test for missing cmake dependencies
> 3.) Build and install each package in isolation and its declared
> dependencies, and run tests to detect missing install dependencies
> I do not know enough about pre-release tests to tell you what happens
> there, I can only tell you what you can do locally.
> cheers,
>   Thibault
> _______________________________________________
> Ros-release mailing list
> Ros-release at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-release

Tully Foote
tfoote at willowgarage.com
(650) 475-2827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20130215/71a13529/attachment-0009.html>

More information about the Ros-release mailing list