autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopkgtest (Debian) |
Fix Released
|
Unknown
|
|||
autopkgtest (Ubuntu) |
Fix Released
|
Undecided
|
Paride Legovini | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Imported from Debian bug http://
Package: autopkgtest
Severity: normal
X-Debbugs-Cc: <email address hidden>
Adding a pocket via --apt-pocket=
_get_default_
construct the sources.list entry for the pocket, which will be in the
form of:
deb <mirror> <default_
The _get_default_
release in the default_release variable, which is the same variable
used to store the --apt-default-
no effect when only one test is present in d/t/control, but when
more than one test is present the tests after the first will have
unwanted/wrong pinning (as if --apt-default-
Related branches
- Brian Murray: Approve
- Ubuntu Release Team: Pending requested
-
Diff: 113 lines (+31/-11)2 files modifiedlib/adt_testbed.py (+14/-6)
tests/autopkgtest (+17/-5)
- Paride Legovini: Pending requested
- Brian Murray: Pending requested
-
Diff: 12751 lines (+6465/-2169) (has conflicts)72 files modified.gitlab-ci.yml (+153/-0)
Makefile (+18/-1)
debian/README.source (+172/-57)
debian/autopkgtest.lintian-overrides (+1/-1)
debian/changelog (+483/-0)
debian/control (+17/-6)
debian/tests/autopkgtest (+13/-0)
debian/tests/control (+126/-11)
debian/tests/docker (+27/-0)
debian/tests/lxc (+35/-0)
debian/tests/lxd (+22/-37)
debian/tests/podman (+27/-0)
debian/tests/podman-init (+27/-0)
debian/tests/schroot (+58/-0)
debian/tests/unshare (+40/-0)
dev/null (+0/-1)
doc/README.package-tests.rst (+208/-63)
doc/README.running-tests.rst (+12/-34)
doc/README.virtualisation-server.rst (+22/-22)
lib/VirtSubproc.py (+100/-11)
lib/adt_testbed.py (+420/-185)
lib/autopkgtest_args.py (+31/-57)
lib/autopkgtest_qemu.py (+358/-42)
lib/in-testbed/README.md (+8/-0)
lib/in-testbed/await-boot.sh (+16/-0)
lib/in-testbed/reboot-prepare.sh (+28/-0)
lib/in-testbed/reboot.sh (+28/-0)
lib/in-testbed/wrapper.sh (+164/-0)
lib/testdesc.py (+167/-207)
lib/unshare-helper (+67/-0)
runner/autopkgtest (+83/-42)
runner/autopkgtest.1 (+19/-39)
setup-commands/create-normal-user (+78/-0)
setup-commands/enable-sudo (+40/-0)
setup-commands/setup-testbed (+220/-40)
ssh-setup/maas (+2/-2)
tests/autopkgtest (+946/-653)
tests/autopkgtest_args (+9/-33)
tests/mypy (+4/-1)
tests/pycodestyle (+2/-1)
tests/pyflakes (+2/-1)
tests/qemu (+43/-1)
tests/shellcheck (+2/-0)
tests/testarchive.py (+1/-0)
tests/testdesc (+56/-379)
tests/testpkg/debian/control (+1/-1)
tests/testpkg/debian/rules (+3/-0)
tools/autopkgtest-build-docker (+363/-0)
tools/autopkgtest-build-docker.1 (+188/-0)
tools/autopkgtest-build-lxc (+2/-0)
tools/autopkgtest-build-lxd (+31/-3)
tools/autopkgtest-build-lxd.1 (+11/-0)
tools/autopkgtest-build-podman (+1/-0)
tools/autopkgtest-build-podman.1 (+1/-0)
tools/autopkgtest-build-qemu (+211/-20)
tools/autopkgtest-build-qemu.1 (+97/-13)
tools/autopkgtest-buildvm-ubuntu-cloud (+77/-32)
tools/autopkgtest-buildvm-ubuntu-cloud.1 (+4/-0)
virt/autopkgtest-virt-docker (+267/-0)
virt/autopkgtest-virt-docker.1 (+173/-0)
virt/autopkgtest-virt-lxc (+49/-38)
virt/autopkgtest-virt-lxd (+27/-5)
virt/autopkgtest-virt-lxd.1 (+4/-0)
virt/autopkgtest-virt-null (+4/-1)
virt/autopkgtest-virt-podman (+1/-0)
virt/autopkgtest-virt-podman.1 (+1/-0)
virt/autopkgtest-virt-qemu (+243/-90)
virt/autopkgtest-virt-qemu.1 (+69/-17)
virt/autopkgtest-virt-schroot (+17/-11)
virt/autopkgtest-virt-ssh.1 (+0/-11)
virt/autopkgtest-virt-unshare (+184/-0)
virt/autopkgtest-virt-unshare.1 (+81/-0)
Changed in autopkgtest (Debian): | |
importance: | Undecided → Unknown |
status: | New → Fix Committed |
Changed in autopkgtest (Debian): | |
status: | Fix Committed → Fix Released |
The ingredients required to hit this bug are:
1. an all-proposed build (--apt- pocket= proposed with no package pinning)
2. multiple tests defined in d/t/control
3. the tests do not allow reusing the same testbed system
Condition 1. means that we don't hit the bug in tests runs triggered
by britney, as those are not all-proposed.