Build failed in Jenkins: raring-server-ec2-daily » amd64,eu-west-1,instance-store,proposed,ubuntu-server-ec2-testing #76

Jenkins Notification devnull at canonical.com
Wed Jul 17 14:11:56 UTC 2013 

See <http://10.189.74.2:8080/job/raring-server-ec2-daily/./ARCH=amd64,REGION=eu-west-1,STORAGE=instance-store,TEST=proposed,label=ubuntu-server-ec2-testing/76/>

------------------------------------------
Started by upstream project "raring-server-ec2-daily" build number 76
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson8304166978194587418.sh
+ echo Running Test amd64 eu-west-1 instance-store for current daily build.
Running Test amd64 eu-west-1 instance-store for current daily build.
+ rm -Rf None i-5ad4da17_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 instance-store -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:instance-store
INFO:root:Retieving ec2 AMI informfation from http://uec-images.ubuntu.com/query/raring/server/daily.current.txt
INFO:root:Found AMI ami-61736c15 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-61736c15
            - #instances: 1
            - size: m1.large
            - region: eu-west-1 
            - placement: None 
            - arch: amd64 
            - storage: instance-store
        
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-61736c15 of size m1.large in region eu-west-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-6cfaea21]
INFO:root:Waiting for reservation to complete
INFO:root:Monitoring for test completion
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
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-133-38.eu-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.1p1 Debian-4
# ec2-54-228-133-38.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.34.168.95' to the list of known hosts.
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130717-1346-a32ad0fc1a9343.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-6cfaea21/host.keys', 'root at ec2-54-228-133-38.eu-west-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-228-133-38.eu-west-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output: 
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130717-1346-a32ad0fc1a9343.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-6cfaea21/host.keys', 'ubuntu at ec2-54-228-133-38.eu-west-1.compute.amazonaws.com', 'echo Hello World']
DEBUG:root:Cmd output: Hello World

INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-228-133-38.eu-west-1.compute.amazonaws.com port 22: Connection timed out
lost connection
ERROR:root:Something bad happened Unable to deploy test executor to instance
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-61736c15
            - #instances: 1
            - size: m1.large
            - region: eu-west-1 
            - placement: None 
            - arch: amd64 
            - storage: instance-store
        
INFO:root:Instance: i-6cfaea21 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