add-on fork rosdistro (mainly dev jobs)

49 views
Skip to first unread message

Manuel Werlberger

unread,
Feb 29, 2016, 5:29:02 AM2/29/16
to ros-sig-buildfarm
Hi,
Finally, all Jenkins jobs are green, except the Jdev_ test job of a sample package. The issue is the rosdep problem which I also had to fix calling bloom on my local machine via https://github.com/mikepurvis/rosdep-generator. Now, Jenkins has the same issues. Before I start hacking something together, is there an official solution/way to resolve this?

In terms of configuration, I entered the custom_rosdep_urls in the source-build.yaml.

the output of the jenkins job:
# BEGIN SECTION: Run Dockerfile - generating devel tasks
11:02:44 + rm -fr /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_build_and_install
11:02:44 + rm -fr /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_build_and_test
11:02:44 + mkdir -p /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_build_and_install
11:02:44 + mkdir -p /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_build_and_test
11:02:44 + docker run --rm --cidfile=/home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_generating_dockers/docker.cid -e=HOME=/home/buildfarm -v /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/ros_buildfarm:/tmp/ros_buildfarm:ro -v /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/catkin_workspace:/tmp/catkin_workspace:ro -v /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_build_and_install:/tmp/docker_build_and_install -v /home/jenkins-slave/workspace/Jdev__catkin_simple__ubuntu_trusty_amd64/docker_build_and_test:/tmp/docker_build_and_test -v /home/jenkins-slave/.ccache:/home/buildfarm/.ccache devel_task_generation.jade_catkin_simple
11:02:48 reading in sources list data from /etc/ros/rosdep/sources.list.d
11:02:48 Hit https://raw.githubusercontent.com/zurich-eye/ze_rosdistro/master/rosdep/osx-homebrew.yaml
11:02:48 Hit https://raw.githubusercontent.com/zurich-eye/ze_rosdistro/master/rosdep/base.yaml
11:02:48 Hit https://raw.githubusercontent.com/zurich-eye/ze_rosdistro/master/rosdep/python.yaml
11:02:48 Hit https://raw.githubusercontent.com/zurich-eye/ze_rosdistro/master/rosdep/ruby.yaml
11:02:48 Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml
11:02:48 Query rosdistro index https://raw.githubusercontent.com/zurich-eye/ze_rosdistro/master/index.yaml
11:02:48 Add distro "jade"
11:02:48 updated cache in /home/buildfarm/.ros/rosdep/sources.cache
11:02:48 Crawling for packages in workspace '/tmp/catkin_workspace/src'
11:02:48 Found the following packages:
11:02:48   - catkin_simple
11:02:48 Package maintainer emails: dthomas@osrfoundation.org william@osrfoundation.org
11:02:50 Always install the following generic dependencies:
11:02:50   - build-essential
11:02:50   - python3
11:02:50   - ros-jade-catkin
11:02:50 Identified the following build dependencies (ignoring packages available from source):
11:02:50   - catkin
11:02:50 Traceback (most recent call last):
11:02:50   File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 196, in resolve_names
11:02:50     rosdep_key, view, installer, os_name, os_code_name)
11:02:50   File "/usr/lib/python3/dist-packages/rosdep2/catkin_support.py", line 81, in resolve_for_os
11:02:50     d = view.lookup(rosdep_key)
11:02:50   File "/usr/lib/python3/dist-packages/rosdep2/lookup.py", line 187, in lookup
11:02:50     return self.rosdep_defs[rosdep_name]
11:02:50 KeyError: 'catkin'
11:02:50
11:02:50 During handling of the above exception, another exception occurred:
11:02:50
11:02:50 Traceback (most recent call last):
11:02:50   File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 212, in <module>
11:02:50     main()
11:02:50   File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 98, in main
11:02:50     debian_pkg_names_building = resolve_names(build_depends, **context)
11:02:50   File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 199, in resolve_names
11:02:50     "Could not resolve the rosdep key '%s'" % rosdep_key)
11:02:50 RuntimeError: Could not resolve the rosdep key 'catkin'
11:02:50 Build step 'Execute shell' marked build as failure


Furthermore, the add-on fork causes to only have few deb pkgs in the beginning and Jrel_sync-packages-to-testing_trusty_amd64 fails complaining that there are <900 jobs. Is it save to remove this check in case of an add-on fork?

Best,
 Manuel

Tully Foote

unread,
Feb 29, 2016, 2:23:26 PM2/29/16
to ros-sig-...@googlegroups.com
On Mon, Feb 29, 2016 at 2:29 AM, Manuel Werlberger <co...@werlberger.org> wrote:
Hi,
Finally, all Jenkins jobs are green, except the Jdev_ test job of a sample package. The issue is the rosdep problem which I also had to fix calling bloom on my local machine via https://github.com/mikepurvis/rosdep-generator. Now, Jenkins has the same issues. Before I start hacking something together, is there an official solution/way to resolve this?

There's a ticket here where we found a workaround that people have used: https://github.com/ros-infrastructure/ros_buildfarm/issues/87 and discussed a more complete solution but have not followed up on the more complete solution. 
This comes from the parameter in your buildfarm_config you should lower your count for your custom repo: https://github.com/ros-infrastructure/ros_buildfarm_config/blob/master/indigo/release-build.yaml#L14  



 

Best,
 Manuel

--
You received this message because you are subscribed to the Google Groups "ros-sig-buildfarm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-buildf...@googlegroups.com.
To post to this group, send email to ros-sig-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ros-sig-buildfarm/62db4056-d2e6-4887-8791-06eaa95a71c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages