Build failed in Jenkins: raring-adt-libgdata » i386,adt #12

[Jenkins Notification]

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

------------------------------------------
Started by upstream project "raring-adt-libgdata" build number 12
[EnvInject] - Loading node environment variables.
Building remotely on alderamin-adt
[adt] $ /bin/sh -xe /tmp/hudson851238115119352906.sh
+ rm -Rf results
+ RELEASE=raring
+ PACKAGE=libgdata
+ OPTS=-s -P
+ cd /home/auto-package-testing/auto-package-testing/bin
+ ./run-adt-test -a i386 -r raring -s -P libgdata
Formatting '/dev/shm/adt/raring-i386-libgdata-20130128_090809.1f7v7x.img', fmt=qcow2 size=7516192768 backing_file='/home/auto-package-testing/cache/disks/pristine-raring-i386-20130128_000933.img' encryption=off cluster_size=65536 
2013-01-28 09:08:09 AM: Info: Waiting 1 seconds before starting VM
2013-01-28 09:08:10 AM: Info: Trying port 54323
2013-01-28 09:08:10 AM: Info: failed to lock port 54323
2013-01-28 09:08:11 AM: Info: Trying port 54324
2013-01-28 09:08:11 AM: Info: failed to lock port 54324
2013-01-28 09:08:12 AM: Info: Trying port 54325
2013-01-28 09:08:12 AM: Info: Successfully locked port 54325
2013-01-28 09:08:12 AM: Info: Trying port 5911
2013-01-28 09:08:12 AM: Info: failed to lock port 5911
2013-01-28 09:08:13 AM: Info: Trying port 5912
2013-01-28 09:08:13 AM: Info: failed to lock port 5912
2013-01-28 09:08:14 AM: Info: Trying port 5913
2013-01-28 09:08:14 AM: Info: Successfully locked port 5913
2013-01-28 09:08:14 AM: Info: Starting raring-i386-libgdata-20130128_090809.1f7v7x.img on port 54325
2013-01-28 09:08:14 AM: Info: Waiting for VM to startup
QEMU 1.0 monitor - type 'help' for more information
(qemu) 2013-01-28 09:08:15 AM: Info: Waiting for testbed initialisation
2013-01-28 09:08:15 AM: Info: Trying to connect to testbed ( Try 1 / 18 )
lost connection
2013-01-28 09:10:52 AM: Info: Trying to connect to testbed ( Try 2 / 18 )
lost connection
2013-01-28 09:13:32 AM: Info: Trying to connect to testbed ( Try 3 / 18 )
lost connection
2013-01-28 09:16:12 AM: Info: Trying to connect to testbed ( Try 4 / 18 )
lost connection
2013-01-28 09:18:52 AM: Info: Trying to connect to testbed ( Try 5 / 18 )
lost connection
2013-01-28 09:21:32 AM: Info: Trying to connect to testbed ( Try 6 / 18 )
lost connection
2013-01-28 09:24:12 AM: Info: Trying to connect to testbed ( Try 7 / 18 )
lost connection
2013-01-28 09:26:52 AM: Info: Trying to connect to testbed ( Try 8 / 18 )
lost connection
2013-01-28 09:29:32 AM: Info: Trying to connect to testbed ( Try 9 / 18 )
lost connection
2013-01-28 09:32:12 AM: Info: Trying to connect to testbed ( Try 10 / 18 )
lost connection
2013-01-28 09:34:52 AM: Info: Trying to connect to testbed ( Try 11 / 18 )
lost connection
2013-01-28 09:37:32 AM: Info: Trying to connect to testbed ( Try 12 / 18 )
lost connection
2013-01-28 09:40:12 AM: Info: Trying to connect to testbed ( Try 13 / 18 )
lost connection
2013-01-28 09:42:52 AM: Info: Trying to connect to testbed ( Try 14 / 18 )
lost connection
2013-01-28 09:45:32 AM: Info: Trying to connect to testbed ( Try 15 / 18 )
lost connection
2013-01-28 09:48:12 AM: Info: Trying to connect to testbed ( Try 16 / 18 )
lost connection
2013-01-28 09:50:52 AM: Info: Trying to connect to testbed ( Try 17 / 18 )
lost connection
2013-01-28 09:53:32 AM: Info: Trying to connect to testbed ( Try 18 / 18 )
lost connection
2013-01-28 09:56:12 AM: Info: Trying to connect to testbed ( Try 19 / 18 )
lost connection
2013-01-28 09:58:42 AM: Failure: Failed to reach the VM after 180s. Exiting.
2013-01-28 09:58:42 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