[Ros-release] Build failures for camera1394 on Groovy
Tully Foote
tfoote at willowgarage.com
Fri Mar 1 09:39:41 UTC 2013
I'm not sure what's going on here. In groovy you will get that error if a
dependency which is supposed to be a ros package doesn't exist on your
path. The tools will then assume it must be a rosdep if it's not an
existing package. I'll look into it tomorrow. I think it might be that the
prerelease is installing the union of build and run depends, skipping the
test_depends. If that's true, then rostest won't be installed, if that's
how it should be will take a trip to the white board with some sketching to
answer.
Tully
On Wed, Feb 27, 2013 at 8:41 PM, Jack O'Quin <jack.oquin at gmail.com> wrote:
> Now I'm seeing a rosdep problem resolving rostest. The manifest declares
> it as a <depend>, not a <rosdep>. Why does it think it's a system
> dependency?
>
>
> http://build.willowgarage.com/job/prerelease_groovy_camera1394_precise_amd64/8/console
>
>
> Installing system dependencies of stacks we're testing
> Install system dependencies of stack camera1394
> Executing command "rosdep install -y camera1394"
>
> ERROR: the following packages/stacks could not have their rosdep keys resolved
> to system dependencies:
> camera1394: Missing resource rostest
> ROS path [0]=/opt/ros/groovy/share/ros
> ROS path [1]=/tmp/install_dir/stack_overlay
> ROS path [2]=/tmp/install_dir/depends_overlay
> ROS path [3]=/tmp/install_dir/depends_on_overlay
> ROS path [4]=/tmp/install_dir/ros_release
> ROS path [5]=/opt/ros/groovy/share
> ROS path [6]=/opt/ros/groovy/stacks
>
> Install system dependencies of stack camera1394
> =========================================
> Failed to execute 'rosdep install -y camera1394'
> =========================================
>
> =========================================
> ERROR: the following packages/stacks could not have their rosdep keys resolved
> to system dependencies:
> camera1394: Missing resource rostest
> ROS path [0]=/opt/ros/groovy/share/ros
> ROS path [1]=/tmp/install_dir/stack_overlay
> ROS path [2]=/tmp/install_dir/depends_overlay
> ROS path [3]=/tmp/install_dir/depends_on_overlay
> ROS path [4]=/tmp/install_dir/ros_release
> ROS path [5]=/opt/ros/groovy/share
> ROS path [6]=/opt/ros/groovy/stacks
>
> =========================================
> ROS_PACKAGE_PATH = /tmp/install_dir/stack_overlay:/tmp/install_dir/depends_overlay:/tmp/install_dir/depends_on_overlay:/tmp/install_dir/ros_release:/opt/ros/groovy/share:/opt/ros/groovy/stacks
> ROS_ROOT = /opt/ros/groovy/share/ros
> PYTHONPATH = /opt/ros/groovy/lib/python2.7/dist-packages
>
> =========================================
>
> Global exception caught. Generating email
> job failed. Check the console output for test failure details.
> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/dist-packages/ros_job_generation-0.1.27-py2.7.egg/EGG-INFO/scripts/run_auto_stack_prerelease.py", line 100, in main
> 'Install system dependencies of stack %s'%stack)
> File "/usr/local/lib/python2.7/dist-packages/ros_job_generation-0.1.27-py2.7.egg/job_generation/jobs_common.py", line 462, in call
> raise Exception('job failed')
> Exception: job failed
>
>
> --
> joq
>
> _______________________________________________
> 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/20130301/a13ac3af/attachment-0008.html>
More information about the Ros-release
mailing list