Build failed in Jenkins: quantal-server-ec2-daily » amd64,eu-west-1,instance-store,simple-user-data,ubuntu-server-ec2-testing #244
Jenkins Notification
devnull at canonical.com
Wed Oct 2 15:02:42 UTC 2013
See <http://10.189.74.2:8080/job/quantal-server-ec2-daily/./ARCH=amd64,REGION=eu-west-1,STORAGE=instance-store,TEST=simple-user-data,label=ubuntu-server-ec2-testing/244/>
------------------------------------------
[...truncated 577 lines...]
Setting up python-gobject-2 (2.28.6-10ubuntu2) ...
Setting up python-gtk2 (2.24.0-3build1) ...
Setting up python-httplib2 (0.7.4-2ubuntu0.1) ...
Setting up python-support (1.0.15) ...
Setting up python-junitxml (0.6-1) ...
Setting up python-keyring (0.9.2-1ubuntu0.2) ...
Setting up python-simplejson (2.6.1-1) ...
Setting up python-lazr.uri (1.0.3-1) ...
Setting up python-wadllib (1.3.0-2) ...
Setting up python-lazr.restfulclient (0.12.0-2) ...
Setting up python-launchpadlib (1.9.12-2) ...
Setting up python-subunit (0.0.8+bzr176-1) ...
Setting up sgml-base (1.26+nmu3ubuntu1) ...
Updating the super catalog...
Setting up subunit (0.0.8+bzr176-1) ...
Setting up xml-core (0.13+nmu1) ...
update-catalog: Suppressing action on super catalog. Invoking trigger instead.
update-catalog: Please rebuild the package being set up with a version of debhelper fixing #477751.
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for python-support ...
Processing triggers for sgml-base ...
Updating the super catalog...
+ cd /tmp
+ bzr branch lp:~ubuntu-server-ec2-testing-dev/+junk/ec2-automated-tests tests
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 73 revisions.
+ cd tests/simple-user-data
+ sudo python -m subunit.run test
+ subunit2junitxml
DEBUG:root:Cmd: ['netstat', '-atuvpn']
DEBUG:root:Cmd output: Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 728/sshd
tcp 0 0 10.240.50.162:38143 91.189.92.177:80 TIME_WAIT -
tcp 0 0 10.240.50.162:53819 91.189.92.201:80 TIME_WAIT -
tcp 0 0 10.240.50.162:22 10.238.127.123:53282 ESTABLISHED 1947/sshd: ubuntu [
tcp 0 0 10.240.50.162:22 10.238.127.123:53278 TIME_WAIT -
tcp 0 0 10.240.50.162:40405 91.189.95.84:80 TIME_WAIT -
tcp 0 0 10.240.50.162:54833 91.189.92.200:80 TIME_WAIT -
tcp 0 0 10.240.50.162:40407 91.189.95.84:80 TIME_WAIT -
tcp6 0 0 :::22 :::* LISTEN 728/sshd
udp 0 0 0.0.0.0:60228 0.0.0.0:* 541/dhclient
udp 0 0 0.0.0.0:68 0.0.0.0:* 541/dhclient
udp6 0 0 :::30377 :::* 541/dhclient
DEBUG:root:Cmd: ['pgrep', 'sshd']
DEBUG:root:Cmd output: 728
1947
2019
DEBUG:root:Cmd: ['cat', '/root/OUTPUT-simple-01.txt']
DEBUG:root:Cmd output: ================ Hello World ================
It is Wed, 02 Oct 2013 14:26:29 +0000
I've been up for 16.98 seconds
==============================================
DEBUG:root:Cmd: ['sudo', '-l', '-U', 'ubuntu']
DEBUG:root:Cmd output: Matching Defaults entries for ubuntu on this host:
env_reset, mail_badpass,
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin
User ubuntu may run the following commands on this host:
(ALL : ALL) ALL
(ALL) NOPASSWD: ALL
(ALL) NOPASSWD: ALL
DEBUG:root:Cmd: ['su', '-c', 'sudo echo Hello World', 'ubuntu']
DEBUG:root:Cmd output: Hello World
+ exit 0
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
read (ec2-54-246-68-246.eu-west-1.compute.amazonaws.com): No route to host
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Instance i-f3268bbc not responding after 1200 seconds - rebooting
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Tests did not complete in 3300 seconds
INFO:root:Tidyup test
INFO:root:Testing failed for
AMI: ami-a0bc5ad7
- #instances: 1
- size: m1.large
- region: eu-west-1
- placement: None
- arch: amd64
- storage: instance-store
INFO:root:Instance: i-f3268bbc Completed: False Errors: True Phase: 5 Keyscan: None
INFO:root:
Test Summary:
Tests to Execute: 1
Tests Completed: 0
Tests Failed: 1
Total Tests Executed: 1
ERROR:root:At least one test case execution failed - please investigate.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
More information about the ubuntu-testing-notifications
mailing list