autopkgtest (5.11)
[PTS] [DDPO]
COMMITS: VCS has seen 14 commits since the debian/5.11 tag
- Git: https://salsa.debian.org/ci-team/autopkgtest.git
-
- Branch: master
- Path: debian/changelog
- Browser: https://salsa.debian.org/ci-team/autopkgtest
- Last scan: 2019-12-02 02:10:10+00
- Next scan: 2019-12-09 14:13:00+00
- Merge requests: 5
- CI pipeline status: success
- Debian changelog in Git:
autopkgtest (5.11) unstable; urgency=medium
[ Dan Streetman ]
* autopkgtest-buildvm-ubuntu-cloud: work with precise and trusty
(LP: #1822331) (Closes: #925966)
[ Sébastien Delafond ]
* Add an optional 6th parameter to autopkgtest-build-qemu, to force a
specific image size
[ Julian Andres Klode ]
* ssh-setup/nova: Run nova show after console-log in debug_failure
[ Iain Lane ]
* setup-testbed: Add the -security pocket for Ubuntu releases
* nova: Use glanceclient to find images
* nova: --key_name is actually --key-name
* setup-testbed: Write preserve_sources_list in the new format
* nova: trim whitespace from server UUID
[ Simon McVittie ]
* autopkgtest-build-qemu: Parse named parameters
* autopkgtest-build-qemu: Allow overriding apt proxy via command-line
[ Simon McVittie ]
* testdesc: Report each unsupported test individually (Closes: #851232)
* setup-testbed: Provide more options for handling /etc/apt/sources.list
(Closes: #933062)
[ Dan Streetman ]
* ssh-setup/nova: allow specifying --image with name or uuid
[ Valentin Vidic ]
* autopkgtest-virt-lxc: accept lxc arguments for ephemeral containers
[ Michael Biebl ]
* Use virtio-rng to passthrough RNG to qemu runner and drop haveged
[ Raphaël Hertzog ]
* qemu: Forward VM's ssh port only to localhost (Closes: #931219)
-- Paul Gevers <elbrus@debian.org> Thu, 05 Sep 2019 09:32:10 +0200
- This branch is 14 commits ahead of tag debian/5.11
- Git log:
commit f4d5ceaf38d207a175571d0ceec8e11db3bfac38
Merge: efb93ac 50706e0
Author: Antonio Terceiro <terceiro@debian.org>
Date: Mon Dec 2 02:02:41 2019 +0000
Merge branch 'shell-fail-harder' into 'master'
lib/adt_testbed.py, runner/autopkgtest: Run --shell-fail in more situations
See merge request ci-team/autopkgtest!68
commit efb93ac3ff0bc06a279523a63fbc71ff46dcb3a9
Merge: ed6f6ec e5b1157
Author: Antonio Terceiro <terceiro@debian.org>
Date: Mon Dec 2 02:01:28 2019 +0000
Merge branch 'rng-tools' into 'master'
setup-testbed: Install rng-tools
See merge request ci-team/autopkgtest!67
commit ed6f6ecfdcda30f6354ec34d1b07742270c88616
Merge: ce039e1 6ac81a0
Author: Antonio Terceiro <terceiro@debian.org>
Date: Mon Dec 2 01:51:33 2019 +0000
Merge branch 'remove-tempdir-unpack' into 'master'
Drop unpacking of dependencies to temporary dir
See merge request ci-team/autopkgtest!65
commit ce039e191a677702ee5d94ab1e27152aac58e260
Author: Antonio Terceiro <terceiro@debian.org>
Date: Thu Nov 28 11:28:32 2019 -0300
.gitlab-ci.yml: avoid duplicating test steps
commit 50706e0e80e3f39673c49da906eb1fcff9890df1
Author: Iain Lane <iain.lane@canonical.com>
Date: Thu Nov 28 12:22:12 2019 +0000
lib/adt_testbed.py, runner/autopkgtest: Run --shell-fail in more situations
If the setup script fails, or if test-dep installation doesn't work, it
can be useful to be able to get into the environment to investigate
directly. This commit makes that possible.
commit e5b11576ad79b538f5cb0acdf0fa857c390e6e38
Author: Iain Lane <iain.lane@canonical.com>
Date: Thu Nov 28 12:16:09 2019 +0000
setup-testbed: Install rng-tools
If a /dev/hwrng is set up - as might be done by cloud providers, or as
we do with autopkgtest-virt-qemu - let's feed /dev/random with it.
commit b7dd30ed431913750d4353cacda8e3ad7406bbaa
Author: Antonio Terceiro <terceiro@debian.org>
Date: Fri Nov 15 10:51:54 2019 -0300
.gitlab-ci.yml: track stable
This way we don't need to update the it on each new release.
commit 6ac81a0cfb30ad0c8eabdb2916a9b6d11d2cc1ee
Author: Antonio Terceiro <terceiro@debian.org>
Date: Thu Nov 14 14:09:44 2019 -0300
Drop unpacking of dependencies to temporary dir
This is a workaround for when you can't install dependencies on the
testbed (e.g. "null" virtualization). It only works for a few types of
packages, because those are hardcoded.
This patch removes that completely, and instead just fails the test
indicating which test dependencies are missing if that's the case.
commit c8c0c6ea00b343934719daf3ee262ec908e19970
Author: Antonio Terceiro <terceiro@debian.org>
Date: Thu Oct 31 09:59:16 2019 +0100
debian/control, debian/tests/control: run wrap-and-sort
commit f4bdbe4856c4483aa851134d2bc0619b9c83f579
Merge: 020ec62 ce4a497
Author: Martin Pitt <mpitt@debian.org>
Date: Tue Oct 8 07:33:32 2019 +0000
Merge branch 'package_arch_regression_fix' into 'master'
autopkgtest: when checking binary pkg arch, allow *-$ARCH-* values also
See merge request ci-team/autopkgtest!64
commit ce4a497a7f0d32c36110c859ae624b93e143d802
Author: Dan Streetman <ddstreet@canonical.com>
Date: Mon Oct 7 13:15:00 2019 -0400
autopkgtest: when checking binary pkg arch, allow *-$ARCH-* values also
The list of possible valid arch strings, provided by:
$ dpkg-architecture -L
can include plain archs like 'amd64' or 'any', but also can contain
'linux-any' or other dash-separated values. So to match those as well
from the awk script, include - as a possible value delimiter, so arch
values are separated by either , or -.
The correct way to check the arch would be to call out to dpkg-architecture
from the awk script, which probably is possible using awk system() but
would have to also check for 'all'. However this entire awk script
is difficult to understand and maintain; I prefer this minor patch
for this regression, and then looking at complete replacement using
something else.
commit 020ec6285a836d20ab799742649712f7224d61c8
Author: Dan Streetman <ddstreet@canonical.com>
Date: Thu Sep 26 07:45:56 2019 -0400
autopkgtest: When finding src pkg, skip binary pkgs for other archs
When looking for the src pkg, the entire Package-List is searched for every
binary package name. However, there are some rare source packages that
provide binary packages for specific arch(s), while the same binary package
is provided by another source packge for a different arch. One example
is the 'binutils' and 'binutils-mipsen' source packages; currently the
'binutils-mipsen' package provides several 'binutils-mips*' named
binary packages for intel archs, while the main 'binutils' source package
provides the same-named binary packages specifically for the mips arch.
In cases such as this, autopkgtest needs to make sure to only consider
source packages that provide the binary for the current testbed arch,
otherwise it will be confused about what source package name and what
version to look for in the archive.
An example of this is: https://launchpad.net/bugs/1845157
LP: #1845157
Closes: #939790
commit 22efd48b113097350102dbe2788b382f38ee2101
Merge: e3db341 747d553
Author: Paul Gevers <elbrus@debian.org>
Date: Thu Sep 26 08:15:10 2019 +0000
Merge branch 'lxd-test' into 'master'
tools/autopkgtest-build-lxd: pass /dev/null on stdin to lxc launch
See merge request ci-team/autopkgtest!62
commit 747d55377c943143f71a56c6decb8e26957f178d
Author: Dan Streetman <ddstreet@canonical.com>
Date: Tue Sep 24 17:16:51 2019 -0400
tools/autopkgtest-build-lxd: pass /dev/null on stdin to lxc launch
Recent changes to lxd cause 'lxc launch' to fail if there is any input on
stdin queued, which is the case (at least) during the 'lxd' autopkgtest
included in this package, which calls autopkgtest-build-lxd from a here
document passed to a shell. It may be the case for other external uses as
well, so it's best to leave the 'lxd' autopkgtest as is and fix the
autopkgtest-build-lxd script to use lxc launch with the new restriction.
The only other call to 'lxc launch' is from autopkgtest-virt-lxd, which
passes it to check_exec(), and that function explicitly sets stdin to
/dev/null, so no change is needed there.
(LP: #1845037)
