JohannesK's profile - activity

I found the problem. For fuerte/groovy you should use the python module "ros-job-generation" instead of the package "job_generation" in the stack ros_release. The "name" of the scripts are the same in both packages though.

I use a modified version of the script "run_auto_stack_prerelease.py" with stacks located in the appropriate *.rosdistro file only. Okay, when you're using the same (original) scripts the mistake should be caused from somewhere else, may be in the modified version of the script. Thanks for help!

I edit my question above to get a better understanding of what am I doing!

Exactly, I search for the scripts they are using to run the pre-release test.

Thank you for your reply!

I focus more on the "pre-release-test" part. I'm looking for the tool which I can use for downloading stacks (plus dependencies) and build them over jenkins, like the jenkins_tools (http://www.ros.org/wiki/jenkins_tools). In the past we used the ros_release stack to run a job on hudson and with electric it worked fine, using fuerte/groovy failed. There are jobs on the willow-jenkins-server with groovy and fuerte (http://build.willowgarage.com/view/pre-release/), I'm wondering which scripts they are using to start them.

Hi,

I try to build a stack using the stack ros_release. When I build packages with electric everything works fine. However, when I try to run it with fuerte or groovy an error occurs:

Global exception caught.
this program assumes that ros is in your variant. Check the console output for test failure details.
Traceback (most recent call last):
  File "/home/user/workspace_jenktool/jenkins_scripts/analyze.py", line 106, in analyze
    rosdistro_obj = rosdistro.Distro(get_rosdistro_file(ros_distro))
  File "/home/user/groovy_workspace/ros_release/rosdistro/src/rosdistro.py", line 444, in __init__
    raise DistroException("this program assumes that ros is in your variant")
DistroException: this program assumes that ros is in your variant

That programm assumes that ros is part of the variants in the distro file, but it isn't. I checked the versions of the stack ros_release in the ros-wiki and it is just available for electric, but not for fuerte/groovy. However, there are different branches in the repo (e.g. fuerte, fuerte_new, groovy, groovy_new) and I am a little bit confused about that.

What stack/tool do I have to use when I want to build a non-catkin-stack with fuerte or groovy. The jenkins_tool is just for catkin-based package, isn't it?

Anyone know?

Cheers, Johannes

EDIT: It is not my purpose to do a release or anything. My purpose is to build existing stacks only. Under this link (http://www.ros.org/wiki/release/Releasing/fuerte) you will find following part:

Pre-release: Run a Hudson on-demand build to make sure that your stack builds! While it is acceptable to release a stack that does not work on all distributions and architectures that are supported by Willow Garage, your stack will be much more useful to the community when it works on all supported platforms. For alternate ways of running the pre-release, see job_generation

When I use the package job_generation I am able to build a package with electric, but neither with fuerte nor groovy and it ends up with the error above. So I assume that the scripts for the pre-release are not the same for electric and fuerte/groovy, because the webinterface works apparently.

I figured it out. The problem was a bug in pbuilder (under lucid) so that the tar-file wasn't create correctly. You can fix it by downloading the appropriate patch.

Hi guys,

I am trying to run the command "run_chroot_local" from the jenkins_tool-package (http://www.ros.org/wiki/jenkins_tools) and get an error.

I run the example for the run_chroot_local command:

Command:

run_chroot_local precise amd64 /home/kuj1pal/workspace prerelease groovy common_msgs

Output:

...
...
apt-show-versions is already the newest version.
The following packages were automatically installed and are no longer required:
  libaccess-bridge-java python-qt4-gl libaccess-bridge-java-jni gnash-common python-opengl
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 75 not upgraded.
++ apt-show-versions python-jenkins-tools
++ awk '{for (i = 0; i < 10; i++)  if ( !match($i, " ") && match($i, "[0-9].[0-9]") ) print $i}'
+ REPOSTAMP='0.0.26-1
0.0.30-1'
+ /bin/echo 'Repo stamp is 0.0.26-1
0.0.30-1'
Repo stamp is 0.0.26-1
0.0.30-1
+ '[' 0.0.26-1 0.0.30-1 '!=' 0.0.26-1 0.0.30-1 ']'
**/usr/bin/chroot_create.sh: line 37: [: too many arguments**
+ /bin/echo '^^^^^^^^^^^^^^^^^^  create_chroot.sh ^^^^^^^^^^^^^^^^^^^^'
^^^^^^^^^^^^^^^^^^  create_chroot.sh ^^^^^^^^^^^^^^^^^^^^
++ cat /tmp/tmp.naNf4IHMNd/basetgz
+ basetgz=/var/cache/pbuilder/jenkins_tools.precise.amd64-0.4.1.tgz
+ rm -rf /tmp/tmp.naNf4IHMNd
+ sudo pbuilder execute --basetgz /var/cache/pbuilder/jenkins_tools.precise.amd64-0.4.1.tgz --bindmounts '/var/cache/pbuilder/ccache /home/kuj1pal/workspace /home/kuj1pal/.ssh' --inputfile /home/kuj1pal/workspace/jenkins_scripts/prerelease -- /home/kuj1pal/workspace/pbuilder-env.sh prerelease
**W: /home/kuj1pal/.pbuilderrc does not exist**
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/jenkins_tools.precise.amd64-0.4.1.tgz]

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
**E: failed to extract /var/cache/pbuilder/jenkins_tools.precise.amd64-0.4.1.tgz to /var/cache/pbuilder/build//22098**

I checked the jenkins_tools.precise.amd64-0.4.1.tgz file and it's empty.

Any ideas?

Cheers, Johannes