Build failed in Jenkins: quantal-server-ec2-daily » amd64,eu-west-1,ebs,simple-user-data,ubuntu-server-ec2-testing #224
Jenkins Notification
devnull at canonical.com
Wed Jul 17 14:27:06 UTC 2013
See <http://10.189.74.2:8080/job/quantal-server-ec2-daily/./ARCH=amd64,REGION=eu-west-1,STORAGE=ebs,TEST=simple-user-data,label=ubuntu-server-ec2-testing/224/>
------------------------------------------
[...truncated 514 lines...]
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-16f0e05b 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: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-16f0e05b 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: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-e30b1497
- #instances: 1
- size: m1.large
- region: eu-west-1
- placement: None
- arch: amd64
- storage: ebs
INFO:root:Instance: i-16f0e05b 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