Build failed in Jenkins: saucy-upgrade-raring-server » amd64,non-lts,server,upgrade-test #5

[Jenkins Notification]

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

------------------------------------------
Started by upstream project "saucy-upgrade-raring-server" build number 5
[EnvInject] - Loading node environment variables.
Building remotely on wazn-upgrade
[upgrade-test] $ /bin/sh -x /tmp/hudson5073600383961861370.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=/home/upgrade-tester/auto-upgrade-tester
+ [ non-lts = non-lts ]
+ LTSPREFIX=
+ ARCHEXT=amd64
+ PROFILENAME=saucy-server-amd64
+ echo Running profile saucy-server-amd64
Running profile saucy-server-amd64
+ python bin/auto-upgrade-tester /home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64
Testing '/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64'
using ssh port: 54322
using VncNum: 5901
Storing the result in '/home/upgrade-tester/auto-upgrade-tester/result/saucy-server-amd64'
2013-07-10 23:04:41.447376 log started
bootstrap()
Not bootstrapping again, we have a cached BaseImage
upgrade()
Starting for upgrade
Starting ['kvm', '-hda', '/home/upgrade-tester//auto-upgrade-tester/test-image.saucy-server-amd64', '-monitor', 'stdio', '-localtime', '-no-reboot', '-net', 'nic,model=virtio', '-net', 'user', '-redir', 'tcp:54322::22', '-vnc', 'localhost:1', '-m', '1536']
Copying '/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64/DistUpgrade.cfg' to image overrides
Copying '/home/upgrade-tester/auto-upgrade-tester/profiles/override.cfg.d/global.cfg' to image overrides
Disabling ForceOverwrite
Using do-release-upgrade for the upgrade
dist-upgrade.py returned: 1
coyping the result
Shuting down the VM
stop
stop pid:  <subprocess.Popen object at 0x1226790>
waiting for qemu to shutdown
poll() returned
qemu stopped
FAILED: upgrade for '/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64'
Failed to upgrade /home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64
Logs can be found here:
 /home/upgrade-tester/auto-upgrade-tester/result/saucy-server-amd64/bootstrap.log
 /home/upgrade-tester/auto-upgrade-tester/result/saucy-server-amd64/main.log
 /home/upgrade-tester/auto-upgrade-tester/result/saucy-server-amd64/apt.log
2013-07-10 23:05:30.747560 log ended.
Duration: 0:00:49.300184
Profile '/home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64' FAILED
stop
Releasing lock: /var/lock/auto-upgrade-tester.54322.lock
Releasing lock: /var/lock/auto-upgrade-tester.5901.lock
+ cp -ar /home/upgrade-tester/auto-upgrade-tester/result/saucy-server-amd64/ <http://10.189.74.2:8080/job/saucy-upgrade-raring-server/./ARCH=amd64,LTS=non-lts,PROFILE=server,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