[Rock-dev] RockBootstrap » next,DebianUnstable: drivers/camera_usb: failed in import phase - Failure!

noreply at dfki.de noreply at dfki.de
Sat Jan 28 01:22:55 CET 2012


RockBootstrap » next,DebianUnstable - Build # 275 - Failure:

drivers/camera_usb: failed in import phase
    'git checkout -b next autobuild/next' returned status 128
    see /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install/log/drivers/camera_usb-import.log for details
    last 10 lines are:

      'USERNAME'='root'
      'VIZKIT_PLUGIN_RUBY_PATH'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install/lib/vizkit:/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install/lib'
      'WORKSPACE'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable'
      '_'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/.gems/bin/autoproj'
      'label'='DebianUnstable'
    
    Sat Jan 28 00:22:55 +0000 2012: running
        git checkout -b next autobuild/next
    fatal: git checkout: updating paths is incompatible with switching branches.
    Did you intend to checkout 'autobuild/next' which can not be resolved as commit?
Build step 'Execute shell' marked build as failure
Email was triggered for: Failure
Sending email for trigger: Failure


Check console output at http://build01.dfki.uni-bremen.de:8080/job/RockBootstrap/./FLAVOR=next,label=DebianUnstable/275/ to view the results.

Complete console output follows:

Started by upstream project "RockBootstrap" build number 275
Building remotely on DebianUnstable
No emails were triggered.
[DebianUnstable] $ /bin/sh -xe /tmp/hudson896601796686813964.sh
+ test xDebianUnstable != xDebianUnstable
+ /home/build/slave_conf/rock_build_from_bootstrap.sh /home/build/rock_buildconf
+ export PATH=/home/build/rock_admin_scripts/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
+ PATH=/home/build/rock_admin_scripts/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
+ CONFIG_DIR=/home/build/slave_conf
++ dirname RockBootstrap/FLAVOR=next,label=DebianUnstable
+ job_basename=RockBootstrap
+ test -f /home/build/slave_conf/RockBootstrap-next.yml
+ configfile=/home/build/slave_conf/default-next.yml
+ test xfalse = xtrue
+ do_incremental=1
+ do_full_cleanup=0
+ test x = xtrue
+ test xauto = xincremental
+ test xauto = xbootstrap
+ test -d dev
+ test -f dev/successful
+ echo 'doing a full build'
doing a full build
+ do_incremental=0
+ test x0 = x1
+ rm -f dev/successful
+ rm -f dev/doc-successful
+ rm -f dev/cleaned
+ rm -f docgen.txt
+ rm -rf api
+ test -d dev/install/cache
+ mkdir -p archive_cache
+ cp -rf dev/install/cache/OpenCV-2.3.0.tar.bz2 dev/install/cache/PCL-1.4.0-Source.tar.bz2 dev/install/cache/cminpack-1.1.3.tar.gz dev/install/cache/flann-1.6.11-src.zip dev/install/cache/sisl_4.4_GPL.tgz dev/install/cache/tinyxml_2_6_2.zip dev/install/cache/yaml-cpp-0.2.5.tar.gz archive_cache
+ test x0 = x0
+ test x0 = x1
+ test -d dev
+ rm -rf dev/install
+ find dev -type d -name build -exec rm -rf '{}' ';' -prune
+ rm -rf dev/.gems dev/autoproj
+ rm -rf dev/autoproj dev/.remotes
+ test -d archive_cache
+ mkdir -p dev/install/cache
+ cp -rf archive_cache/OpenCV-2.3.0.tar.bz2 archive_cache/PCL-1.4.0-Source.tar.bz2 archive_cache/cminpack-1.1.3.tar.gz archive_cache/flann-1.6.11-src.zip archive_cache/sisl_4.4_GPL.tgz archive_cache/tinyxml_2_6_2.zip archive_cache/yaml-cpp-0.2.5.tar.gz dev/install/cache
+ /bin/bash -ex rock-build-incremental /home/build/rock_buildconf /home/build/slave_conf/default-next.yml
+ source rock-build-common.sh
++ set -e
+ BUILDCONF_GIT=/home/build/rock_buildconf
+ BUILDCONF_FILE=/home/build/slave_conf/default-next.yml
+ MAIL_HEADER=
+ MAIL_ADDRESS=
+ MAIL_SMTP=
+ argument_checks
+ test -z /home/build/rock_buildconf
+ test -n ''
+ COMMON_ARGS=
+ export AUTOPROJ_BOOTSTRAP_IGNORE_NONEMPTY_DIR=1
+ AUTOPROJ_BOOTSTRAP_IGNORE_NONEMPTY_DIR=1
+ test -z ''
+ export AUTOPROJ_OSDEPS_MODE=all
+ AUTOPROJ_OSDEPS_MODE=all
+ update
+ test -d dev/autoproj
+ prepare_buildconf_git
+ test -f /home/build/slave_conf/default-next.yml
+ rm -rf buildconf
+ git clone /home/build/rock_buildconf buildconf
Cloning into buildconf...
done.
+ cd buildconf
+ cp -f /home/build/slave_conf/default-next.yml config.yml
+ git add -f config.yml
+ git commit -a -m 'build server configuration'
[master 3102eaa] build server configuration
 1 files changed, 13 insertions(+), 0 deletions(-)
 create mode 100644 config.yml
+ cd ..
+ mkdir -p dev
+ BUILDCONF_GIT=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/buildconf
+ cd dev
+ test -d autoproj
+ rm -f autoproj_bootstrap
+ wget http://rock-robotics.org/autoproj_bootstrap
--2012-01-28 00:22:05--  http://rock-robotics.org/autoproj_bootstrap
Resolving rock-robotics.org (rock-robotics.org)... 46.252.18.78, 2a00:1158:0:300:3cfb::1
Connecting to rock-robotics.org (rock-robotics.org)|46.252.18.78|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58717 (57K) [text/plain]
Saving to: `autoproj_bootstrap'

     0K .......... .......... .......... .......... .......... 87%  603K 0s
    50K .......                                               100% 48.5M=0.08s

2012-01-28 00:22:05 (690 KB/s) - `autoproj_bootstrap' saved [58717/58717]

+ ruby autoproj_bootstrap --no-color git /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/buildconf
    autodetecting the operating system
autoproj: installing a proper Ruby environment (this can take a long time)
autoproj: installing autoproj and its dependencies (this can take a long time)
  installing/updating RubyGems dependencies: autobuild
  installing/updating RubyGems dependencies: autoproj
  autodetecting the operating system
  checking out autoproj main configuration
  Access method to import data from gitorious.org (git, http or ssh): git
  Which prepackaged software (a.k.a. 'osdeps') should autoproj install automatically (all, ruby, os, none) ? all
autoproj: updating remote definitions of package sets
  checking out git:git://gitorious.org/rock-toolchain/package_set.git push_to=git at gitorious.org:/rock-toolchain/package_set.git
  checking out git:git://gitorious.org/rock/package_set.git push_to=git at gitorious.org:/rock/package_set.git
  checking out git:git://gitorious.org/rock-tutorials/package_set.git push_to=git at gitorious.org:/rock-tutorials/package_set.git
  rock.toolchain: auto-importing git:git://gitorious.org/orocos-toolchain/autoproj.git push_to=git at gitorious.org:/orocos-toolchain/autoproj.git
  checking out git:git://gitorious.org/orocos-toolchain/autoproj.git push_to=git at gitorious.org:/orocos-toolchain/autoproj.git
  rock.toolchain: auto-importing git:git://gitorious.org/rock-base/package_set.git push_to=git at gitorious.org:/rock-base/package_set.git
  checking out git:git://gitorious.org/rock-base/package_set.git push_to=git at gitorious.org:/rock-base/package_set.git

autoproj: loading ...
run 'autoproj reconfigure' to change configuration options
and use 'autoproj switch-config' to change the remote source for
autoproj's main build configuration
  Which flavor of Rock do you want to use ? next
  WARN: osdeps definition for boost, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  WARN: osdeps definition for hoe, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  the target operating system for Orocos/RTT (gnulinux or xenomai): gnulinux
  which CORBA implementation should the RTT use ? omniorb
  Do you need compatibility with OCL ? (yes or no): false
  WARN: 
  WARN: the following packages are using a branch which is incompatible with the flavors
  WARN: they are included in (as e.g. using the 'next' branch while being included only on 'master').
  WARN: they got switched back to master
  WARN:   base/templates/bundle, bundles/rock, control/orogen/auv_control, control/orogen/auv_rel_pos_controller, drivers/laserscanner_sick, drivers/orogen/camera_v4l, drivers/orogen/laserscanner_sick, drivers/orogen/qualisys, drivers/orogen/sonar_tritech, drivers/orogen/transformer, drivers/qualisys, drivers/sonar_tritech, gui/map2d, image_processing/jpeg_conversion, image_processing/orogen/stereo, image_processing/stereo, slam/orogen/graph_slam, slam/orogen/tilt_scan, slam/polygonnet, tools/log_tools, tutorials/orogen/tut_sensor


autoproj bootstrap successfully finished

To further use autoproj and the installed software, you
must add the following line at the bottom of your .bashrc:
  source /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/env.sh

WARNING: autoproj will not work until your restart all
your consoles, or run the following in them:
  $ source /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/env.sh

To import and build the packages, you can now run
  autoproj update
  autoproj build

The resulting software is installed in
  /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install

+ . ./env.sh
++ export RUBYOPT=-rubygems
++ RUBYOPT=-rubygems
++ export GEM_HOME=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/.gems
++ GEM_HOME=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/.gems
++ export PATH=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/.gems/bin:/home/build/rock_admin_scripts/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
++ PATH=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/.gems/bin:/home/build/rock_admin_scripts/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
+ test -n /home/build/slave_conf/default-next.yml
+ cp -f /home/build/slave_conf/default-next.yml autoproj/config.yml
+ autoproj full-build --no-color
  Access method to import data from gitorious.org (git, http or ssh): git
  autodetecting the operating system
  Which prepackaged software (a.k.a. 'osdeps') should autoproj install automatically (all, ruby, os, none) ? all
  autodetecting the operating system
autoproj: updating remote definitions of package sets
  looking for RubyGems updates
  updating rock.toolchain
  updating rock
  updating rock.tutorials
  rock.toolchain: auto-importing orocos.toolchain
  updating orocos.toolchain
  rock.toolchain: auto-importing rock.base
  updating rock.base

autoproj: loading ...
run 'autoproj reconfigure' to change configuration options
and use 'autoproj switch-config' to change the remote source for
autoproj's main build configuration
  Which flavor of Rock do you want to use ? next
  WARN: osdeps definition for boost, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  WARN: osdeps definition for hoe, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  the target operating system for Orocos/RTT (gnulinux or xenomai): gnulinux
  which CORBA implementation should the RTT use ? omniorb
  Do you need compatibility with OCL ? (yes or no): false
  WARN: 
  WARN: the following packages are using a branch which is incompatible with the flavors
  WARN: they are included in (as e.g. using the 'next' branch while being included only on 'master').
  WARN: they got switched back to master
  WARN:   base/templates/bundle, bundles/rock, control/orogen/auv_control, control/orogen/auv_rel_pos_controller, drivers/laserscanner_sick, drivers/orogen/camera_v4l, drivers/orogen/laserscanner_sick, drivers/orogen/qualisys, drivers/orogen/sonar_tritech, drivers/orogen/transformer, drivers/qualisys, drivers/sonar_tritech, gui/map2d, image_processing/jpeg_conversion, image_processing/orogen/stereo, image_processing/stereo, slam/orogen/graph_slam, slam/orogen/tilt_scan, slam/polygonnet, tools/log_tools, tutorials/orogen/tut_sensor

autoproj: importing and loading selected packages
  updating base/orogen/types
  updating base/scripts
  updating base/templates/cmake_lib
  updating base/templates/cmake_vizkit_widget
  updating base/templates/vizkit
  updating base/types
  updating base/types_ruby
  updating basics_tutorial/message_driver
  updating basics_tutorial/orogen/message_consumer
  updating basics_tutorial/orogen/message_producer
  updating control/motor_controller
  updating control/orogen/skid4_control
  updating control/orogen/trajectory_follower
  updating control/orogen/waypoint_navigation
  updating control/trajectory_follower
  updating control/waypoint_navigation
  updating drivers/aggregator
  updating drivers/camera_firewire
  updating drivers/camera_interface
  updating drivers/camera_prosilica
  checking out drivers/camera_usb
  WARN: import from git://gitorious.org/rock-drivers/camera_usb.git failed, falling back to using http for all packages on gitorious.org
  checking out drivers/camera_usb
Build failed
drivers/camera_usb: failed in import phase
    'git checkout -b next autobuild/next' returned status 128
    see /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install/log/drivers/camera_usb-import.log for details
    last 10 lines are:

      'USERNAME'='root'
      'VIZKIT_PLUGIN_RUBY_PATH'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install/lib/vizkit:/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/install/lib'
      'WORKSPACE'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable'
      '_'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/DebianUnstable/dev/.gems/bin/autoproj'
      'label'='DebianUnstable'
    
    Sat Jan 28 00:22:55 +0000 2012: running
        git checkout -b next autobuild/next
    fatal: git checkout: updating paths is incompatible with switching branches.
    Did you intend to checkout 'autobuild/next' which can not be resolved as commit?
Build step 'Execute shell' marked build as failure
Email was triggered for: Failure
Sending email for trigger: Failure



More information about the Rock-dev mailing list