Build failed in Jenkins: raring-server-ec2-daily » amd64,eu-west-1,ebs,proposed,ubuntu-server-ec2-testing #74
Jenkins Notification
devnull at canonical.com
Wed Jul 10 14:17:25 UTC 2013
See <http://10.189.74.2:8080/job/raring-server-ec2-daily/./ARCH=amd64,REGION=eu-west-1,STORAGE=ebs,TEST=proposed,label=ubuntu-server-ec2-testing/74/>
------------------------------------------
Started by upstream project "raring-server-ec2-daily" build number 74
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson202942029955201650.sh
+ echo Running Test amd64 eu-west-1 ebs for current daily build.
Running Test amd64 eu-west-1 ebs for current daily build.
+ rm -Rf None i-5e605213_test_remote.pyc tests
+ 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 revision(s).
+ execute-ubuntu-ec2-test -r eu-west-1 -s ebs -a amd64 -R raring -t tests proposed
INFO:root:Creating test for size:m1.large for arch:amd64 in region:eu-west-1 placement:any root storage:ebs
INFO:root:Retieving ec2 AMI informfation from http://uec-images.ubuntu.com/query/raring/server/daily.current.txt
INFO:root:Found AMI ami-69332f1d
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing
AMI: ami-69332f1d
- #instances: 1
- size: m1.large
- region: eu-west-1
- placement: None
- arch: amd64
- storage: ebs
INFO:root:Creating ec2 Connection
INFO:root:Creating keypair for test
INFO:root:Creating security group for test
INFO:root:Starting instances
INFO:root:Executing 1 instance for ami ami-69332f1d of size m1.large in region eu-west-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-b61316fb]
INFO:root:Waiting for reservation to complete
INFO:root:Monitoring for test completion
INFO:root:Current testing phase: 1
read (ec2-54-228-104-115.eu-west-1.compute.amazonaws.com): No route to host
read (ec2-54-228-104-115.eu-west-1.compute.amazonaws.com): No route to host
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
# ec2-54-228-104-115.eu-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.1p1 Debian-4
# ec2-54-228-104-115.eu-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.1p1 Debian-4
Warning: Permanently added the RSA host key for IP address '10.32.1.37' to the list of known hosts.
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130710-1407-d8002c3ecb474d.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/ebs/i-b61316fb/host.keys', 'root at ec2-54-228-104-115.eu-west-1.compute.amazonaws.com', 'echo Hello World']
DEBUG:root:Cmd output: Please login as the user "ubuntu" rather than the user "root".
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130710-1407-d8002c3ecb474d.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/ebs/i-b61316fb/host.keys', 'ubuntu at ec2-54-228-104-115.eu-west-1.compute.amazonaws.com', 'echo Hello World']
DEBUG:root:Cmd output: Hello World
INFO:root:Current testing phase: 3
scp: /tmp/done: No such file or directory
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-228-104-115.eu-west-1.compute.amazonaws.com port 22: Connection timed out
ERROR:root:Something bad happened Unable to execute in-instance tests.
INFO:root:Tidyup test
INFO:root:Testing failed for
AMI: ami-69332f1d
- #instances: 1
- size: m1.large
- region: eu-west-1
- placement: None
- arch: amd64
- storage: ebs
INFO:root:Instance: i-b61316fb Completed: False Errors: False Phase: 3 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