Build failed in Jenkins: precise-upgrade-oneiric-server » i386,non-lts,server-tasks,upgrade-test #331

Jenkins Notification devnull at canonical.com
Wed Dec 12 17:38:06 UTC 2012


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

------------------------------------------
Started by upstream project "precise-upgrade-oneiric-server" build number 331
[EnvInject] - Loading node environment variables.
Building remotely on aldebaran-upgrade
No emails were triggered.
[upgrade-test] $ /bin/sh -x /tmp/hudson1446433633676575398.sh
+ rm -Rf auto-upgrade-testing results
+ BRANCH=auto-upgrade-testing
+ [ -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 62 revisions.
+ cd auto-upgrade-testing
+ LTSPREFIX=
+ ARCHEXT=
+ BASEDIR=/var/home/upgrade-tester/auto-upgrade-tester
+ [ non-lts = non-lts ]
+ LTSPREFIX=
+ ARCHEXT=i386
+ PROFILENAME=server-tasks-i386
+ [ i386 = i386 ]
+ [ ! -e /var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks-i386 ]
+ PROFILENAME=server-tasks
+ echo Running profile server-tasks
Running profile server-tasks
+ python bin/auto-upgrade-tester /var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks
Testing '/var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks'
Port 54322 already in use. Skipping!
Port 54323 already locked. Skipping!
using ssh port: 54324
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!
Port 5915 already in use. Skipping!
Port 5916 already locked. Skipping!
Port 5917 already in use. Skipping!
using VncNum: 5918
Storing the result in '/var/home/upgrade-tester/auto-upgrade-tester/result/server-tasks'
2012-12-12 17:07:33.539148 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.server-tasks', '-monitor', 'stdio', '-localtime', '-no-reboot', '-net', 'nic,model=virtio', '-net', 'user', '-redir', 'tcp:54324::22', '-vnc', 'localhost:18', '-m', '1536']
Copying '/var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks/DistUpgrade.cfg' to image overrides
Copying '/var/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: 255
coyping the result
Shuting down the VM
stop
stop pid:  <subprocess.Popen object at 0x255c590>
waiting for qemu to shutdown
Not stopped after 600s, killing 
qemu stopped
FAILED: upgrade for '/var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks'
Failed to upgrade /var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks
Logs can be found here:
 /var/home/upgrade-tester/auto-upgrade-tester/result/server-tasks/bootstrap.log
 /var/home/upgrade-tester/auto-upgrade-tester/result/server-tasks/main.log
 /var/home/upgrade-tester/auto-upgrade-tester/result/server-tasks/apt.log
2012-12-12 17:38:04.406814 log ended.
Duration: 0:30:30.867666
Profile '/var/home/upgrade-tester/auto-upgrade-tester/profiles/server-tasks' FAILED
stop
Releasing lock: /var/lock/auto-upgrade-tester.54324.lock
Releasing lock: /var/lock/auto-upgrade-tester.5918.lock
+ cp -ar /var/home/upgrade-tester/auto-upgrade-tester/result/server-tasks/ <http://10.189.74.2:8080/job/precise-upgrade-oneiric-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



More information about the ubuntu-testing-notifications mailing list