Build failed in Jenkins: raring-adt-aptdaemon » i386,adt #86

[Jenkins Notification]

See <http://10.189.74.2:8080/job/raring-adt-aptdaemon/./ARCH=i386,label=adt/86/>

------------------------------------------
Started by upstream project "raring-adt-aptdaemon" build number 86
[EnvInject] - Loading node environment variables.
Building remotely on alderamin-adt
[adt] $ /bin/sh -xe /tmp/hudson4993547012012401449.sh
+ rm -Rf results
+ RELEASE=raring
+ PACKAGE=aptdaemon
+ OPTS=-s -P
+ cd /home/auto-package-testing/auto-package-testing/bin
+ ./run-adt-test -a i386 -r raring -s -P aptdaemon
Formatting '/dev/shm/adt/raring-i386-aptdaemon-20121215_035026.img', fmt=qcow2 size=4294967296 backing_file='/home/auto-package-testing/cache/disks/pristine-raring-i386-20121214_080528.img' encryption=off cluster_size=65536 
2012-12-15 03:50:26 AM: Info: Waiting 18 seconds before starting VM
2012-12-15 03:50:44 AM: Info: Trying port 54323
2012-12-15 03:50:44 AM: Info: failed to lock port 54323
2012-12-15 03:50:46 AM: Info: Trying port 54324
2012-12-15 03:50:46 AM: Info: failed to lock port 54324
2012-12-15 03:50:47 AM: Info: Trying port 54325
2012-12-15 03:50:47 AM: Info: Successfully locked port 54325
2012-12-15 03:50:47 AM: Info: Trying port 5911
2012-12-15 03:50:47 AM: Info: failed to lock port 5911
2012-12-15 03:50:48 AM: Info: Trying port 5912
2012-12-15 03:50:48 AM: Info: failed to lock port 5912
2012-12-15 03:50:49 AM: Info: Trying port 5913
2012-12-15 03:50:49 AM: Info: Successfully locked port 5913
2012-12-15 03:50:49 AM: Info: Starting raring-i386-aptdaemon-20121215_035026.img on port 54325
2012-12-15 03:50:49 AM: Info: Waiting for VM to startup
2012-12-15 03:50:50 AM: Info: Waiting for testbed initialisation
2012-12-15 03:50:50 AM: Info: Trying to connect to testbed ( Try 1 / 18 )
QEMU 1.0 monitor - type 'help' for more information
(qemu) lost connection
2012-12-15 03:51:29 AM: Info: Trying to connect to testbed ( Try 2 / 18 )
lost connection
2012-12-15 03:51:39 AM: Info: Trying to connect to testbed ( Try 3 / 18 )
lost connection
2012-12-15 03:54:19 AM: Info: Trying to connect to testbed ( Try 4 / 18 )
lost connection
2012-12-15 03:56:59 AM: Info: Trying to connect to testbed ( Try 5 / 18 )
lost connection
2012-12-15 03:59:39 AM: Info: Trying to connect to testbed ( Try 6 / 18 )
lost connection
2012-12-15 04:02:19 AM: Info: Trying to connect to testbed ( Try 7 / 18 )
lost connection
2012-12-15 04:04:59 AM: Info: Trying to connect to testbed ( Try 8 / 18 )
lost connection
2012-12-15 04:07:39 AM: Info: Trying to connect to testbed ( Try 9 / 18 )
lost connection
2012-12-15 04:10:19 AM: Info: Trying to connect to testbed ( Try 10 / 18 )
lost connection
2012-12-15 04:12:59 AM: Info: Trying to connect to testbed ( Try 11 / 18 )
lost connection
2012-12-15 04:15:39 AM: Info: Trying to connect to testbed ( Try 12 / 18 )
lost connection
2012-12-15 04:18:19 AM: Info: Trying to connect to testbed ( Try 13 / 18 )
lost connection
2012-12-15 04:20:59 AM: Info: Trying to connect to testbed ( Try 14 / 18 )
lost connection
2012-12-15 04:23:39 AM: Info: Trying to connect to testbed ( Try 15 / 18 )
lost connection
2012-12-15 04:26:19 AM: Info: Trying to connect to testbed ( Try 16 / 18 )
lost connection
2012-12-15 04:28:59 AM: Info: Trying to connect to testbed ( Try 17 / 18 )
lost connection
2012-12-15 04:31:39 AM: Info: Trying to connect to testbed ( Try 18 / 18 )
lost connection
2012-12-15 04:34:19 AM: Info: Trying to connect to testbed ( Try 19 / 18 )
lost connection
2012-12-15 04:36:49 AM: Failure: Failed to reach the VM after 180s. Exiting.
2012-12-15 04:36:49 AM: 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