=?UTF-8?Q?Build_failed_in_Jenkins:_raring-adt-apport_=C2=BB_i386, adt_#43?=
Jenkins Notification
devnull at canonical.com
Sat Jan 5 14:24:38 UTC 2013
See <http://10.189.74.2:8080/job/raring-adt-apport/./ARCH=i386,label=adt/43/>
------------------------------------------
Started by upstream project "raring-adt-apport" build number 43
[EnvInject] - Loading node environment variables.
Building remotely on alderamin-adt
[adt] $ /bin/sh -xe /tmp/hudson8671729879155468410.sh
+ rm -Rf results
+ RELEASE=raring
+ PACKAGE=apport
+ OPTS=-s -P
+ cd /home/auto-package-testing/auto-package-testing/bin
+ ./run-adt-test -a i386 -r raring -s -P apport
Formatting '/dev/shm/adt/raring-i386-apport-20130105_142018.kuLp6J.img', fmt=qcow2 size=4294967296 backing_file='/home/auto-package-testing/cache/disks/pristine-raring-i386-20130105_080627.img' encryption=off cluster_size=65536
2013-01-05 02:20:18 PM: Info: Waiting 46 seconds before starting VM
2013-01-05 02:21:04 PM: Info: Trying port 54323
2013-01-05 02:21:04 PM: Info: failed to lock port 54323
2013-01-05 02:21:05 PM: Info: Trying port 54324
2013-01-05 02:21:05 PM: Info: Successfully locked port 54324
2013-01-05 02:21:05 PM: Info: Trying port 5911
2013-01-05 02:21:05 PM: Info: failed to lock port 5911
2013-01-05 02:21:06 PM: Info: Trying port 5912
2013-01-05 02:21:06 PM: Info: Successfully locked port 5912
2013-01-05 02:21:06 PM: Info: Starting raring-i386-apport-20130105_142018.kuLp6J.img on port 54324
2013-01-05 02:21:06 PM: Info: Waiting for VM to startup
QEMU 1.0 monitor - type 'help' for more information
(qemu) 2013-01-05 02:21:07 PM: Info: Waiting for testbed initialisation
2013-01-05 02:21:07 PM: Info: Trying to connect to testbed ( Try 1 / 18 )
lost connection
2013-01-05 02:21:48 PM: Info: Trying to connect to testbed ( Try 2 / 18 )
lost connection
2013-01-05 02:21:58 PM: Info: Trying to connect to testbed ( Try 3 / 18 )
lost connection
2013-01-05 02:22:08 PM: Info: Trying to connect to testbed ( Try 4 / 18 )
lost connection
2013-01-05 02:22:18 PM: Info: Trying to connect to testbed ( Try 5 / 18 )
lost connection
2013-01-05 02:22:28 PM: Info: Trying to connect to testbed ( Try 6 / 18 )
lost connection
2013-01-05 02:22:38 PM: Info: Trying to connect to testbed ( Try 7 / 18 )
lost connection
2013-01-05 02:22:48 PM: Info: Trying to connect to testbed ( Try 8 / 18 )
lost connection
2013-01-05 02:22:58 PM: Info: Trying to connect to testbed ( Try 9 / 18 )
lost connection
2013-01-05 02:23:08 PM: Info: Trying to connect to testbed ( Try 10 / 18 )
lost connection
2013-01-05 02:23:18 PM: Info: Trying to connect to testbed ( Try 11 / 18 )
lost connection
2013-01-05 02:23:28 PM: Info: Trying to connect to testbed ( Try 12 / 18 )
lost connection
2013-01-05 02:23:38 PM: Info: Trying to connect to testbed ( Try 13 / 18 )
lost connection
2013-01-05 02:23:48 PM: Info: Trying to connect to testbed ( Try 14 / 18 )
lost connection
2013-01-05 02:23:58 PM: Info: Trying to connect to testbed ( Try 15 / 18 )
lost connection
2013-01-05 02:24:08 PM: Info: Trying to connect to testbed ( Try 16 / 18 )
lost connection
2013-01-05 02:24:18 PM: Info: Trying to connect to testbed ( Try 17 / 18 )
lost connection
2013-01-05 02:24:28 PM: Info: Trying to connect to testbed ( Try 18 / 18 )
lost connection
2013-01-05 02:24:38 PM: Info: Trying to connect to testbed ( Try 19 / 18 )
lost connection
2013-01-05 02:24:38 PM: Failure: Failed to reach the VM after 180s. Exiting.
2013-01-05 02:24:38 PM: Info: Cleaning up
+ 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