Build failed in Jenkins: precise-adt-maas » amd64,maas-lenovo-lab #1
Jenkins Notification
devnull at canonical.com
Tue Nov 6 20:15:49 UTC 2012
See <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/1/>
------------------------------------------
Started by upstream project "precise-adt-maas" build number 1
[EnvInject] - Loading node environment variables.
Building remotely on lenovo-RD230-01
[maas-lenovo-lab] $ /bin/sh -xe /tmp/hudson3829831657535213733.sh
+ rm -Rf *
+ RELEASE=precise
+ PACKAGE=maas
+ PPA=ppa:maas-maintainers/dailybuilds
+ PACKAGING_BRANCH=lp:~matsubara/maas/qa-lab-tests
+ OPTS=-d -p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests
+ cd /var/lib/jenkins/auto-package-testing/bin
+ ./run-adt-test -a amd64 -r precise -d -p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests maas
-a amd64 -r precise -d -p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests -- maas
-r precise -d -p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests -- maas
-d -p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests -- maas
+ RUN_OPTS= -d
+ shift
+ true
+ echo -p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests -- maas
-p ppa:maas-maintainers/dailybuilds -b lp:~matsubara/maas/qa-lab-tests -- maas
+ PPA=ppa:maas-maintainers/dailybuilds
+ RUN_OPTS= -d -p "ppa:maas-maintainers/dailybuilds"
+ shift 2
+ true
+ echo -b lp:~matsubara/maas/qa-lab-tests -- maas
-b lp:~matsubara/maas/qa-lab-tests -- maas
+ [ 0 -ne 0 ]
+ BRANCH=lp:~matsubara/maas/qa-lab-tests
+ RUN_OPTS= -d -p "ppa:maas-maintainers/dailybuilds" -b "lp:~matsubara/maas/qa-lab-tests"
+ shift 2
+ true
+ echo -- maas
-- maas
+ shift
+ break
+ PKGNAME=maas
+ mktemp -d /tmp/adt-amd64.XXXXXX
+ TDIR=/tmp/adt-amd64.ZOgyFL
+ readlink -f /var/tmp/adt/jenkins/disks/pristine-precise-amd64.img
+ DISKPATH=/var/tmp/adt/jenkins/disks/pristine-precise-amd64.img
+ basename /var/tmp/adt/jenkins/disks/pristine-precise-amd64.img
+ DISKNAME=pristine-precise-amd64.img
+ SEED=/var/tmp/adt/jenkins/disks/pristine-precise-amd64.img.seed
+ date +%Y%m%d_%H%M%S
+ BCKNAME=precise-amd64-maas-20121106_151453.img
+ mkdir -p /var/tmp/adt/jenkins/disks
+ BCKPATH=/var/tmp/adt/jenkins/disks/precise-amd64-maas-20121106_151453.img
+ DEFAULT_KEY=/var/tmp/adt/jenkins/disks/adtkey
+ qemu-img create -f qcow2 -o backing_file=/var/tmp/adt/jenkins/disks/pristine-precise-amd64.img /var/tmp/adt/jenkins/disks/precise-amd64-maas-20121106_151453.img
qemu-img: Could not open '/var/tmp/adt/jenkins/disks/pristine-precise-amd64.img'
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2012-11-06 15:14:54: Info: Cleaning up\n
2012-11-06 15:14:54: Info: Cleaning up
+ [ -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20121106_151453.img.pid ]
+ rm -f /var/lock/adt/ssh.54322.lock
+ rm -f /var/lock/adt/vnc.4.lock
+ [ -d /tmp/adt-amd64.ZOgyFL ]
+ rm -Rf /tmp/adt-amd64.ZOgyFL
+ exit 0
+ RET=0
+ [ 0 -eq 2 ]
+ exit 0
Archiving artifacts
ERROR: No artifacts found that match the file pattern "results/*stderr,results/*stdout,results/*log,results/log,results/*.crash". Configuration error?
ERROR: 'results/*stderr' doesn't match anything: even 'results' doesn't exist
Build step 'Archive the artifacts' changed build result to FAILURE
More information about the ubuntu-testing-notifications
mailing list