Build failed in Jenkins: saucy-upgrade-raring-server » i386,non-lts,server-tasks,upgrade-test #14

[Jenkins Notification]

See <http://10.189.74.2:8080/job/saucy-upgrade-raring-server/./ARCH=i386,LTS=non-lts,PROFILE=server-tasks,label=upgrade-test/14/>

------------------------------------------
Started by upstream project "saucy-upgrade-raring-server" build number 14
[EnvInject] - Loading node environment variables.
Building remotely on aldebaran-upgrade
[upgrade-test] $ /bin/sh -x /tmp/hudson8285867861670174136.sh
+ rm -Rf auto-upgrade-testing results
+ BRANCH=auto-upgrade-testing
+ distro-info -d
+ RELEASE=saucy
+ [ -d auto-upgrade-testing ]
+ bzr branch lp:auto-upgrade-testing
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data.  See "bzr help launchpad-login".
Branched 74 revisions.
+ cd auto-upgrade-testing
+ LTSPREFIX=
+ ARCHEXT=
+ BASEDIR=/var/home/upgrade-tester/auto-upgrade-tester
+ [ non-lts = non-lts ]
+ LTSPREFIX=
+ ARCHEXT=i386
+ PROFILENAME=saucy-server-tasks-i386
+ echo Running profile saucy-server-tasks-i386
Running profile saucy-server-tasks-i386
+ python bin/auto-upgrade-tester /var/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-tasks-i386
Testing '/var/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-tasks-i386'
using ssh port: 54322
Port 5901 already in use. Skipping!
Port 5902 already in use. Skipping!
Port 5903 already in use. Skipping!
Port 5904 already in use. Skipping!
Port 5905 already in use. Skipping!
Port 5906 already in use. Skipping!
Port 5907 already in use. Skipping!
Port 5908 already in use. Skipping!
Port 5909 already in use. Skipping!
Port 5910 already in use. Skipping!
Port 5911 already in use. Skipping!
Port 5912 already in use. Skipping!
Port 5913 already in use. Skipping!
Port 5914 already in use. Skipping!
using VncNum: 5915
Storing the result in '/var/home/upgrade-tester/auto-upgrade-tester/result/saucy-server-tasks-i386'
2013-07-15 08:16:36.889448 log started
bootstrap()
Not bootstrapping again, we have a cached BaseImage
upgrade()
Starting for upgrade
Starting ['kvm', '-hda', '/var/home/upgrade-tester/auto-upgrade-tester/test-image.saucy-server-tasks-i386', '-monitor', 'stdio', '-localtime', '-no-reboot', '-net', 'nic,model=virtio', '-net', 'user', '-redir', 'tcp:54322::22', '-vnc', 'localhost:15', '-m', '1536']
Could not start image after 900s, exiting
FAILED: upgrade for '/var/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-tasks-i386'
Failed to upgrade /var/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-tasks-i386
Logs can be found here:
 /var/home/upgrade-tester/auto-upgrade-tester/result/saucy-server-tasks-i386/bootstrap.log
 /var/home/upgrade-tester/auto-upgrade-tester/result/saucy-server-tasks-i386/main.log
 /var/home/upgrade-tester/auto-upgrade-tester/result/saucy-server-tasks-i386/apt.log
2013-07-15 08:31:51.865036 log ended.
Duration: 0:15:14.975588
Profile '/var/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-tasks-i386' FAILED
stop
stop pid:  <subprocess.Popen object at 0x1422610>
waiting for qemu to shutdown
Not stopped after 600s, killing 
qemu stopped
Releasing lock: /var/lock/auto-upgrade-tester.54322.lock
Releasing lock: /var/lock/auto-upgrade-tester.5915.lock
+ cp -ar /var/home/upgrade-tester/auto-upgrade-tester/result/saucy-server-tasks-i386/ <http://10.189.74.2:8080/job/saucy-upgrade-raring-server/./ARCH=i386,LTS=non-lts,PROFILE=server-tasks,label=upgrade-test/ws/results>
Archiving artifacts
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE