Build failed in Jenkins: precise-server-ec2-daily » i386,eu-west-1,ebs,simple-user-data,ubuntu-server-ec2-testing #299

Jenkins Notification devnull at canonical.com
Thu Oct 3 12:13:50 UTC 2013 

See <http://10.189.74.2:8080/job/precise-server-ec2-daily/./ARCH=i386,REGION=eu-west-1,STORAGE=ebs,TEST=simple-user-data,label=ubuntu-server-ec2-testing/299/>

------------------------------------------
[...truncated 395 lines...]
ldconfig deferred processing now taking place
Processing triggers for python-support ...
+ 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
+ subunit2junitxml
+ sudo python -m subunit.run test
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      601/sshd        
tcp        0      0 10.37.171.8:49577       91.189.95.84:80         TIME_WAIT   -               
tcp        0      0 10.37.171.8:49575       91.189.95.84:80         TIME_WAIT   -               
tcp        0      0 10.37.171.8:22          10.238.127.123:48725    ESTABLISHED 1574/sshd: ubuntu [
tcp        0      0 10.37.171.8:44265       91.189.92.176:80        TIME_WAIT   -               
tcp6       0      0 :::22                   :::*                    LISTEN      601/sshd        
udp        0      0 0.0.0.0:68              0.0.0.0:*                           453/dhclient3   

DEBUG:root:Cmd: ['pgrep', 'sshd']
DEBUG:root:Cmd output: 601
1574
1649

DEBUG:root:Cmd: ['cat', '/root/OUTPUT-simple-01.txt']
DEBUG:root:Cmd output: ================ Hello World ================
    It is Thu, 03 Oct 2013 11:19:14 +0000
        I've been up for 59.68 seconds
==============================================

DEBUG:root:Cmd: ['sudo', '-l', '-U', 'ubuntu']
DEBUG:root:Cmd output: Matching Defaults entries for ubuntu on this host:
    env_reset,
    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) NOPASSWD: ALL

DEBUG:root:Cmd: ['su', '-c', 'sudo echo Hello World', 'ubuntu']
DEBUG:root:Cmd output: Hello World

+ exit 0
ssh: connect to host ec2-54-217-45-139.eu-west-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 4
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root: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-fdceadb2 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:Tests did not complete in 3300 seconds
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-aa9e78dd
            - #instances: 1
            - size: m1.small
            - region: eu-west-1 
            - placement: None 
            - arch: i386 
            - storage: ebs
        
INFO:root:Instance: i-fdceadb2 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