[Rock-dev] RockBootstrap » next,Ubuntu1104: tutorials/orogen/rock_tutorial: failed in import phase - Failure!

noreply at dfki.de noreply at dfki.de
Tue Apr 24 06:56:15 CEST 2012 

RockBootstrap » next,Ubuntu1104 - Build # 398 - Failure:

tutorials/orogen/rock_tutorial: failed in import phase
    'git merge f75b2e45468097c53988d084207c728cad9d6b37' returned status 1
    see /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/dev/install/log/tutorials/orogen/rock_tutorial-import.log for details
    last 10 lines are:

      '_'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/dev/.gems/bin/autoproj'
      'label'='Ubuntu1104'
    
    Tue Apr 24 04:56:15 +0000 2012: running
        git merge f75b2e45468097c53988d084207c728cad9d6b37
    error: The following untracked working tree files would be overwritten by merge:
    	tasks/CMakeLists.txt
    Please move or remove them before you can merge.
    Updating 41a6775..f75b2e4
    Aborting
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=Ubuntu1104/398/ to view the results.

Complete console output follows:

[...truncated 60 lines...]
+ 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 eac2943] 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/Ubuntu1104/buildconf
+ cd dev
+ test x = xtrue
+ test -d autoproj
+ rm -f autoproj_bootstrap
+ wget http://rock-robotics.org/autoproj_bootstrap
--2012-04-24 04:55:13--  http://rock-robotics.org/autoproj_bootstrap
Resolving rock-robotics.org... 46.252.18.78, 2a00:1158:0:300:3cfb::1
Connecting to 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%  599K 0s
    50K .......                                               100%  273K=0.1s

2012-04-24 04:55:13 (520 KB/s) - `autoproj_bootstrap' saved [58717/58717]

+ ruby autoproj_bootstrap --no-color git /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/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


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/Ubuntu1104/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/Ubuntu1104/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/Ubuntu1104/dev/install

+ . ./env.sh
++ export RUBYOPT=-rubygems
++ RUBYOPT=-rubygems
++ export GEM_HOME=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/dev/.gems
++ GEM_HOME=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/dev/.gems
++ export PATH=/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/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/Ubuntu1104/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
+ test x = xtrue
+ 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

autoproj: importing and loading selected packages
  updating base/orogen/types
  updating base/scripts
  updating base/templates/bundle
  updating base/templates/cmake_lib
  updating base/templates/cmake_vizkit_widget
  updating base/templates/doc
  WARN: base/templates/doc from rock.base does not have a manifest
  updating base/templates/vizkit
  updating base/types
  updating base/types_ruby
  updating bundles/rock
  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
  updating drivers/camera_usb
  updating drivers/canbus
  updating drivers/controldev
  updating drivers/dvl_teledyne
  updating drivers/dynamixel
  WARN: import from git://gitorious.org/rock-drivers/dynamixel.git failed, falling back to using http for all packages on gitorious.org
  updating drivers/dynamixel
  updating drivers/fog_kvh
  updating drivers/hokuyo
  updating drivers/iCharger
  updating drivers/iodrivers_base
  updating drivers/mb500
  updating drivers/orogen/aggregator
  updating drivers/orogen/camera_base
  updating drivers/orogen/camera_firewire
  updating drivers/orogen/camera_prosilica
  updating drivers/orogen/camera_usb
  updating drivers/orogen/canbus
  updating drivers/orogen/controldev
  updating drivers/orogen/dvl_teledyne
  updating drivers/orogen/dynamixel
  updating drivers/orogen/fog_kvh
  updating drivers/orogen/gps
  updating drivers/orogen/hokuyo
  updating drivers/orogen/iodrivers_base
  updating drivers/orogen/parport
  updating drivers/orogen/taskmon
  updating drivers/orogen/transformer
  updating drivers/orogen/wifimon
  updating drivers/orogen/xsens_imu
  updating drivers/parport
  updating drivers/transformer
  updating drivers/xsens_imu
  updating eigen3
  updating external/cminpack
  updating external/libply
  updating external/opencv
  updating external/sisl
  updating external/tinyxml
  WARN: external/tinyxml from rock does not have a manifest
  updating external/yaml-cpp
  updating gui/rock_widget_collection
  updating gui/vizkit
  updating image_processing/frame_helper
  updating image_processing/jpeg_conversion
  updating image_processing/libelas
  updating image_processing/orogen/image_preprocessing
  updating image_processing/orogen/stereo
  updating image_processing/stereo
  updating multiagent/fipa_acl
  updating orogen
  updating planning/corridor_navigation
  updating planning/corridor_planner
  updating planning/nav_graph_search
  updating planning/orogen/corridor_planner
  updating planning/vfh_star
  updating rtt
  updating slam/envire
  updating slam/flann
  updating slam/hogman
  updating slam/orogen/graph_slam
  updating slam/pcl
  updating slam/pose_ekf
  updating slam/quater_ikf
  updating tools/log_tools
  updating tools/logger
  updating tools/orocos.rb
  updating tools/pocolog
  updating tools/port_proxy
  updating tools/roby
  updating tools/service_discovery
  updating tutorials/designer_widget_tutorial
  updating tutorials/message_driver
  updating tutorials/orogen/message_consumer
  updating tutorials/orogen/message_producer
  updating tutorials/orogen/rock_tutorial
Build failed
tutorials/orogen/rock_tutorial: failed in import phase
    'git merge f75b2e45468097c53988d084207c728cad9d6b37' returned status 1
    see /home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/dev/install/log/tutorials/orogen/rock_tutorial-import.log for details
    last 10 lines are:

      '_'='/home/build/jenkins/workspace/RockBootstrap/FLAVOR/next/label/Ubuntu1104/dev/.gems/bin/autoproj'
      'label'='Ubuntu1104'
    
    Tue Apr 24 04:56:15 +0000 2012: running
        git merge f75b2e45468097c53988d084207c728cad9d6b37
    error: The following untracked working tree files would be overwritten by merge:
    	tasks/CMakeLists.txt
    Please move or remove them before you can merge.
    Updating 41a6775..f75b2e4
    Aborting
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