Build failed in Jenkins: lucid-server-ec2-daily » i386,ap-southeast-1,ebs,ubuntu-server-ec2-testing #6

Jenkins Notification devnull at canonical.com
Thu Feb 2 11:22:46 UTC 2012 

See <http://10.189.74.2:8080/job/lucid-server-ec2-daily/./ARCH=i386,REGION=ap-southeast-1,STORAGE=ebs,label=ubuntu-server-ec2-testing/6/>

------------------------------------------
[...truncated 429 lines...]

Setting up python-crypto (2.0.1+dfsg1-4ubuntu2) ...

Setting up python-gtk2 (2.17.0-0ubuntu2) ...

Setting up python-junitxml (0.5-1) ...

Setting up python-testtools (0.9.2-1) ...

Setting up xfonts-encodings (1:1.0.3-1) ...
Setting up xfonts-utils (1:7.5+2) ...

Setting up x-ttcidfont-conf (32) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Updating font configuration of x-ttcidfont-conf...
Cleaning up category cmap..
Processing triggers for python-central ...

Cleaning up category cid..
Cleaning up category truetype..
Updating category truetype..
Updating category cid..
Updating category cmap..
Setting up python-subunit (0.0.5-1) ...

Setting up bzrtools (2.1.0-1) ...

Setting up python-paramiko (1.7.6-2) ...

Processing triggers for python-central ...
Setting up subunit (0.0.5-1) ...
Processing triggers for libc-bin ...
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 59 revision(s).
+ 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      484/sshd        
tcp        0      1 10.128.139.94:41609     91.189.90.11:80         FIN_WAIT1   -               
tcp        0      0 10.128.139.94:41608     91.189.90.11:80         TIME_WAIT   -               
tcp        0    544 10.128.139.94:22        176.34.199.1:49108      ESTABLISHED 1283/sshd: ubuntu [
tcp6       0      0 :::22                   :::*                    LISTEN      484/sshd        
udp        0      0 0.0.0.0:68              0.0.0.0:*                           380/dhclient3   

DEBUG:root:Cmd: ['pgrep', 'sshd']
DEBUG:root:Cmd output: 484
1283
1348

DEBUG:root:Cmd: ['cat', '/root/OUTPUT-simple-01.txt']
DEBUG:root:Cmd output: ================ Hello World ================
    It is Thu, 02 Feb 2012 10:57:17 +0000
        I've been up for 37.32 seconds
==============================================

DEBUG:root:Cmd: ['sudo', '-l', '-U', 'ubuntu']
DEBUG:root:Cmd output: Matching Defaults entries for ubuntu on this host:
    env_reset

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
cp: cannot stat `/var/log/cloud-init.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init.log
cp: cannot stat `/var/log/cloud-init-output.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init-output.log
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:Instance i-212b3474 not responding after 1200 seconds - rebooting
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
INFO:root:Current testing phase: 5
# ec2-175-41-178-3.ap-southeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-175-41-178-3.ap-southeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '175.41.178.3' to the list of known hosts.
cp: cannot stat `/var/log/cloud-init.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init.log
cp: cannot stat `/var/log/cloud-init-output.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init-output.log
INFO:root:Host ssh-dss key validated for instance i-212b3474 (ec2-175-41-175-237.ap-southeast-1.compute.amazonaws.com)
INFO:root:Host ssh-rsa key validated for instance i-212b3474 (ec2-175-41-175-237.ap-southeast-1.compute.amazonaws.com)
INFO:root:Current testing phase: 6
INFO:root:Current testing phase: 6
INFO:root:Current testing phase: 6
INFO:root:Current testing phase: 6
INFO:root:Current testing phase: 6
INFO:root:Current testing phase: 6
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-320f4b60
            - #instances: 1
            - size: m1.small
            - region: ap-southeast-1 
            - placement: None 
            - arch: i386 
            - storage: ebs
        
INFO:root:Instance: i-212b3474 Completed: True Errors: True Phase: 6 Keyscan: True
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.
Archiving artifacts
Recording test results

More information about the ubuntu-testing-notifications mailing list