Build failed in Jenkins: raring-adt-pango1.0 » amd64,adt #6

[Jenkins Notification]

See <http://10.189.74.2:8080/job/raring-adt-pango1.0/./ARCH=amd64,label=adt/6/>

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