maas-devel team mailing list archive

Thread
Date
Build failed in Jenkins: precise-adt-maas-daily » amd64,maas-lenovo-lab #21

To: maas-devel@xxxxxxxxxxxxxxxxxxx
From: Jenkins Notification <devnull@xxxxxxxxxxxxx>
Date: Mon, 11 Mar 2013 23:29:15 +0000 (UTC)
In-reply-to: <1296452972.682.1362958150747.JavaMail.jenkins@jiufeng>
See <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/21/>

------------------------------------------
[...truncated 937 lines...]
adt-run: trace1: $     pwd >&3
adt-run: trace1: $     set +e; test -f debian/tests/control; echo $? >&3
+ spec=/tmp/tmp.5LyZ0aDPB1/ubtree1-build/real-tree
+ pwd
+ origpwd=/tmp/tmp.5LyZ0aDPB1/ubtree1-ubtree
+ cd /tmp/tmp.5LyZ0aDPB1/ubtree1-build
+ TMPDIR=/tmp/tmp.5LyZ0aDPB1/ubtree1-build/tmpdir
+ rm -rf -- /tmp/tmp.5LyZ0aDPB1/ubtree1-build/tmpdir
+ export TMPDIR
+ mkdir -- /tmp/tmp.5LyZ0aDPB1/ubtree1-build/tmpdir
+ rm -rf /tmp/tmp.5LyZ0aDPB1/ubtree1-build/real-tree
+ mkdir /tmp/tmp.5LyZ0aDPB1/ubtree1-build/real-tree
+ cp -rP --preserve=timestamps,links -- /tmp/tmp.5LyZ0aDPB1/ubtree1-ubtree/. /tmp/tmp.5LyZ0aDPB1/ubtree1-build/real-tree/.
+ cd real-tree/.
+ pwd
+ set +e
+ test -f debian/tests/control
+ echo 1
adt-run: trace1: ** blame += arg:/home/ubuntu/packaging.precise.sru/debian/tests/maas-control
adt-run: trace: & ubtree1t-maas-package-test: constructed; path=debian/tests/maas-package-test
adt-run: trace: & ubtree1t-maas-package-test:  .depends=['maas', 'maas-dhcp', 'maas-dns', 'maas-cli', 'python-nose', 'bzr', 'python-testtools', 'python-yaml', 'juju', 'python-pip', 'python-zmq']
adt-run: trace: * <ubtree:ubtree1> build not needed
adt-run: trace: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ builds done.
adt-run: trace: * reset
adt-run: trace: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests ...
adt-run: trace: @@@@@@@@@@@@@@@@@@@@ test control control0
adt-run: trace1: ** needs_reset, previously=True
adt-run: trace: @@@@@@@@@@@@@@@@@@@@ test ubtree ubtree1
adt-run: trace1: ** needs_reset, previously=True
adt-run: trace1: ** blame += arg:.
adt-run: trace1: ** blame += arg:/home/ubuntu/packaging.precise.sru/debian/tests/maas-control
adt-run: trace: & ubtree1t-maas-package-test: constructed; path=debian/tests/maas-package-test
adt-run: trace: & ubtree1t-maas-package-test:  .depends=['maas', 'maas-dhcp', 'maas-dns', 'maas-cli', 'python-nose', 'bzr', 'python-testtools', 'python-yaml', 'juju', 'python-pip', 'python-zmq']
adt-run: trace: @@@@@@@@@@ run_tests ...
adt-run: trace: & ubtree1t-maas-package-test: preparing
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency maas
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency maas
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency maas-dhcp
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency maas-dhcp
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency maas-dns
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency maas-dns
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency maas-cli
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency maas-cli
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency python-nose
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency python-nose
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency bzr
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency bzr
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency python-testtools
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency python-testtools
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency python-yaml
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency python-yaml
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency juju
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency juju
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency python-pip
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency python-pip
adt-run: trace: & ubtree1t-maas-package-test:  processing dependency python-zmq
adt-run: trace: & ubtree1t-maas-package-test:   literal dependency python-zmq
adt-run: trace1: ** prepare1, modified=True, deps_processed=[], deps_new=['maas', 'maas-dhcp', 'maas-dns', 'maas-cli', 'python-nose', 'bzr', 'python-testtools', 'python-yaml', 'juju', 'python-pip', 'python-zmq']
adt-run: trace1: ** prepare2, deps_new=['maas', 'maas-dhcp', 'maas-dns', 'maas-cli', 'python-nose', 'bzr', 'python-testtools', 'python-yaml', 'juju', 'python-pip', 'python-zmq']
adt-run: trace: * publish
adt-run: trace: $ ftparchive: sh -ec <SCRIPT> x /root/adt-log//binaries /root/.autopkgtest/gpg
adt-run: trace1: $     
adt-run: trace1: $       exec >&2
adt-run: trace1: $       cd "$1"
adt-run: trace1: $       apt-ftparchive packages . >Packages
adt-run: trace1: $       gzip <Packages >Packages.gz
adt-run: trace1: $       apt-ftparchive release . >Release
adt-run: trace1: $       rm -f Release.gpg
adt-run: trace1: $       gpg --homedir="$2" --batch --detach-sign --armour -o Release.gpg Release
adt-run: trace1: $       gpg --homedir="$2" --batch --export >archive-key.pgp
adt-run: trace1: $     		
adt-run: trace: $ apt-key: sh -ec <SCRIPT>
adt-run: trace1: $     
adt-run: trace1: $       exec 3>&1 >&2
adt-run: trace1: $       apt-key add archive-key.pgp
adt-run: trace1: $       echo "deb file:///tmp/tmp.5LyZ0aDPB1/binaries/ /" >/etc/apt/sources.list.d/autopkgtest.list
adt-run: trace1: $       if [ "x`ls /var/lib/dpkg/updates`" != x ]; then
adt-run: trace1: $         echo >&2 "/var/lib/dpkg/updates contains some files, aargh"; exit 1
adt-run: trace1: $       fi
adt-run: trace1: $       apt-get -q -o quiet=true -o APT::Get::Assume-Yes=true -o Debug::pkgProblemResolver=true -o APT::Get::force-yes=true update >&2
adt-run: trace1: $       cat /var/lib/dpkg/status >&3
adt-run: trace1: $     		
OK
Ign file:  InRelease
Get:1 file:  Release.gpg [198 B]
Get:2 file:  Release [1,202 B]
Ign file:  Translation-en_US
Ign file:  Translation-en
Ign http://archive.ubuntu.com precise InRelease
Ign http://ppa.launchpad.net precise InRelease
Ign http://security.ubuntu.com precise-security InRelease
Ign http://archive.ubuntu.com precise-updates InRelease
Hit http://ppa.launchpad.net precise Release.gpg
Hit http://security.ubuntu.com precise-security Release.gpg
Hit http://ppa.launchpad.net precise Release
Hit http://archive.ubuntu.com precise Release.gpg
Hit http://security.ubuntu.com precise-security Release
Hit http://archive.ubuntu.com precise-updates Release.gpg
Hit http://ppa.launchpad.net precise/main Sources
Hit http://security.ubuntu.com precise-security/main Sources
Hit http://archive.ubuntu.com precise Release
Hit http://ppa.launchpad.net precise/main amd64 Packages
Hit http://security.ubuntu.com precise-security/universe Sources
Hit http://archive.ubuntu.com precise-updates Release
Hit http://ppa.launchpad.net precise/main i386 Packages
Hit http://security.ubuntu.com precise-security/main amd64 Packages
Hit http://archive.ubuntu.com precise/main Sources
Ign http://ppa.launchpad.net precise/main TranslationIndex
Hit http://security.ubuntu.com precise-security/universe amd64 Packages
Hit http://archive.ubuntu.com precise/universe Sources
Hit http://security.ubuntu.com precise-security/main i386 Packages
Hit http://archive.ubuntu.com precise/restricted Sources
Hit http://security.ubuntu.com precise-security/universe i386 Packages
Hit http://archive.ubuntu.com precise/multiverse Sources
Hit http://security.ubuntu.com precise-security/main TranslationIndex
Hit http://archive.ubuntu.com precise/main amd64 Packages
Hit http://security.ubuntu.com precise-security/universe TranslationIndex
Hit http://archive.ubuntu.com precise/universe amd64 Packages
Hit http://security.ubuntu.com precise-security/main Translation-en
Hit http://archive.ubuntu.com precise/restricted amd64 Packages
Hit http://security.ubuntu.com precise-security/universe Translation-en
Hit http://archive.ubuntu.com precise/multiverse amd64 Packages
Hit http://archive.ubuntu.com precise/main i386 Packages
Hit http://archive.ubuntu.com precise/universe i386 Packages
Ign http://ppa.launchpad.net precise/main Translation-en_US
Hit http://archive.ubuntu.com precise/restricted i386 Packages
Ign http://ppa.launchpad.net precise/main Translation-en
Hit http://archive.ubuntu.com precise/multiverse i386 Packages
Hit http://archive.ubuntu.com precise/main TranslationIndex
Hit http://archive.ubuntu.com precise/multiverse TranslationIndex
Hit http://archive.ubuntu.com precise/restricted TranslationIndex
Hit http://archive.ubuntu.com precise/universe TranslationIndex
Hit http://archive.ubuntu.com precise-updates/main Sources
Hit http://archive.ubuntu.com precise-updates/universe Sources
Hit http://archive.ubuntu.com precise-updates/main amd64 Packages
Hit http://archive.ubuntu.com precise-updates/universe amd64 Packages
Hit http://archive.ubuntu.com precise-updates/main i386 Packages
Hit http://archive.ubuntu.com precise-updates/universe i386 Packages
Hit http://archive.ubuntu.com precise-updates/main TranslationIndex
Hit http://archive.ubuntu.com precise-updates/universe TranslationIndex
Hit http://archive.ubuntu.com precise/main Translation-en
Hit http://archive.ubuntu.com precise/multiverse Translation-en
Hit http://archive.ubuntu.com precise/restricted Translation-en
Hit http://archive.ubuntu.com precise/universe Translation-en
Hit http://archive.ubuntu.com precise-updates/main Translation-en
Hit http://archive.ubuntu.com precise-updates/universe Translation-en
Reading package lists...
adt-run: trace: * publish reinstall checking...
adt-run: trace: * publish install...
adt-run: trace: * publish done
adt-run: trace1: **  installing dependencies ['maas', 'maas-dhcp', 'maas-dns', 'maas-cli', 'python-nose', 'bzr', 'python-testtools', 'python-yaml', 'juju', 'python-pip', 'python-zmq']
adt-run: trace: dependencies: install-deps: satisfying maas, maas-dhcp, maas-dns, maas-cli, python-nose, bzr, python-testtools, python-yaml, juju, python-pip, python-zmq
adt-run: trace: dependencies: install-deps: running ['/usr/lib/pbuilder/pbuilder-satisfydepends-classic', '--binary-all', '--internal-chrootexec', '/root/adt-log//satdep-auxverb', '-c', '/root/adt-log//deps.dsc']
 -> Attempting to parse the build-deps 
 -> Considering build-dep maas
   -> Trying maas
       -> Cannot install maas; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 maas : Depends: maas-region-controller but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
E: Could not satisfy build-dependency.
blame: arg:. arg:/home/ubuntu/packaging.precise.sru/debian/tests/maas-control arg:. arg:/home/ubuntu/packaging.precise.sru/debian/tests/maas-control
badpkg: dependency install failed, exit code 2
adt-run: erroneous package: dependency install failed, exit code 2
adt-run: trace: ** stop
adt-run: trace: ** close, scratch=tb-scratch~/tmp/tmp.5LyZ0aDPB1:-/|/tmp/tmp.5LyZ0aDPB1/!
+ RC=12
+ [ 12 -eq 20 ]
+ [ 0 -eq 1 ]
+ [ -x /home/ubuntu/adt-export-result ]
+ RES=PASS
+ [ 12 -gt 0 ]
+ RES=FAIL
+ /home/ubuntu/adt-export-result -D /root/adt-log maas FAIL
+ chown -R ubuntu /root/adt-log
+ chmod og+r /var/log/syslog
+ chmod og+r /var/crash/*
+ true
+ exit 12
+ RET=12
+ [ 0 -eq 1 ]
+ [ 12 -gt 0 ]
+ log_failure_msg adt-run exited with status 12.
+ log_msg Failure: adt-run exited with status 12.\n
+ date +%F %X
+ printf 2013-03-11 19:29:10: Failure: adt-run exited with status 12.\n
2013-03-11 19:29:10: Failure: adt-run exited with status 12.
+ [ 0 -eq 0 ]
+ mkdir -p <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ dirname /root/adt-log
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -p 54323 -t -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /root; find /root/adt-log -type f -empty | xargs rm -Rf
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.
sudo: unable to resolve host autopkgtest
+ scp -r -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -P 54323 ubuntu@localhost:/root/adt-log/*
    /var/crash/*crash /var/log/syslog <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ true
+ log_info_msg Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ log_msg Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results\n>
+ date +%F %X
+ printf 2013-03-11 19:29:12: Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results\n>
2013-03-11 19:29:12: Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ [ -n 2013-03-11_23-25-41 ]
+ log_info_msg Updating Jenkins results
+ log_msg Info: Updating Jenkins results\n
+ date +%F %X
+ printf 2013-03-11 19:29:12: Info: Updating Jenkins results\n
2013-03-11 19:29:12: Info: Updating Jenkins results
+ rsync -a <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results/precise_amd64_maas_20130311-232912.result> /precise/out/
rsync: mkdir "/precise/out" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
+ true
+ [ 0 -eq 0 ]
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -p 54323 -t -o BatchMode=yes -l ubuntu localhost sudo poweroff
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.
sudo: unable to resolve host autopkgtest
+ exit 12
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2013-03-11 19:29:12: Info: Cleaning up\n
2013-03-11 19:29:12: Info: Cleaning up
+ [ -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130311_192539.a4ljrA.img.pid ]
+ cat /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130311_192539.a4ljrA.img.pid
+ kill -9 7047
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130311_192539.a4ljrA.img.pid
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130311_192539.a4ljrA.img
+ rm -f /var/lock/adt/ssh.54323.lock
+ rm -f /var/lock/adt/vnc.5911.lock
+ [ -d /tmp/adt-amd64.I7Qqzc ]
+ rm -Rf /tmp/adt-amd64.I7Qqzc
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-*.img*
+ find /var/lock/adt -name *.lock -mtime +1
+ exit 12
Build step 'Execute shell' marked build as failure
Archiving artifacts
Follow ups

Jenkins build is back to normal : precise-adt-maas-daily » amd64,maas-lenovo-lab #22
From: Jenkins Notification, 2013-03-12
References

Build failed in Jenkins: precise-adt-maas-daily » amd64,maas-lenovo-lab #20
From: Jenkins Notification, 2013-03-10