Build failed in Jenkins: sru_kernel-saucy-virtual_amd64-kvm-virtual #66

Jenkins Notification devnull at canonical.com
Wed Oct 30 10:02:57 UTC 2013


See <http://10.189.74.2:8080/job/sru_kernel-saucy-virtual_amd64-kvm-virtual/66/>

------------------------------------------
Started by user psivaa
[EnvInject] - Loading node environment variables.
Building remotely on alderamin
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
[sru_kernel-saucy-virtual_amd64-kvm-virtual] $ /bin/bash -x /tmp/hudson490096576852178350.sh
+ SRUHOME=/var/lib/ubuntu-iso-testing/kernel-sru
+ bzr pull -d /var/lib/ubuntu-iso-testing/kernel-sru/branches/tests
Using saved parent location: http://bazaar.launchpad.net/~ue-qa-kernel-tests-infrastructure-dev/ue-qa-kernel-tests-infrastructure/trunk/
No revisions or tags to pull.
+ '[' -z '' ']'
+ bash -x /var/lib/ubuntu-iso-testing/kernel-sru/branches/tests/kernel-sru/jenkins-script-virtual-kteam.sh -s /var/lib/ubuntu-iso-testing/kernel-sru -r saucy -t virtual -w <http://10.189.74.2:8080/job/sru_kernel-saucy-virtual_amd64-kvm-virtual/ws/> -v generic-amd64 -p amd64 -c 10.98.0.1
+ set +x
Step1 to run on clean-saucy-generic-amd64
Formatting '/var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk0.qcow2', fmt=qcow2 size=8589934592 backing_file='/var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk0.pristine.qcow2' backing_fmt='qcow2' encryption=off cluster_size=65536 
error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

error: Failed to start domain clean-saucy-generic-amd64
error: Unable to allow access for disk path /var/lib/ubuntu-iso-testing/kernel-sru/clean-saucy-generic-amd64/disk1.img: No such file or directory

FAIL virsh start clean-saucy-generic-amd64 failed

+ exit 1
Build step 'Execute shell' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts
Recording test results
Description set: 



More information about the ubuntu-testing-notifications mailing list