Add new autopkgtest policy: it determines the autopkgtests for a
source package (its own, direct reverse binary dependencies, and
Testsuite-Triggers), requests tests via AMQP, fetches results from swift, and
keeps track of pending tests between run. This also caches the downloaded
results from swift, as re-dowloading them all is very expensive.
This introduces two new hints:
* force-badtest pkg/ver[/arch]: Failing results for that package will be
ignored. This is useful to deal with broken tests that get imported from
Debian or are from under-maintained packages, or broke due to some
infrastructure changes. These are long-lived usually.
* force-skiptest pkg/ver: Test results *triggered by* that package (i. e.
reverse dependencies) will be ignored. This is mostly useful for landing
packages that trigger a huge amount of tests (glibc, perl) where some tests
are just too flaky to get them all passing, and one just wants to land it
after the remaining failures have been checked. This should be used rarely
and the hints should be removed immediately again.
Add integration tests that call britney in various scenarios on constructed
fake archives, with mocked AMQP and Swift results.
- use relative paths
- set Ubuntu architectures
- make all output files series specific
- mark -proposed as a partial suite
- set mindays to 0 for all urgencies
- drop tpu and pu
- disable smooth updates
- disable removals of obsolete source packages
- disable components, using old merged package lists for now
Possibly, Britney should support this somewhat more gracefully. But
start with this work around for now.
Signed-off-by: Niels Thykier <niels@thykier.net>
Done as kFreeBSD is not a release architecture and it has started to
block migration of release related changes. I have kept it out of
"BREAK_ARCHES" as I do not yet see a reason to add it there.
Signed-off-by: Niels Thykier <niels@thykier.net>
Martin Pitt
Colin Watson
Jonathan Wiltshire
Emilio Pozuelo Monfort
Niels Thykier
Adam D. Barratt
Andreas Barth
Julien Cristau
Philipp Kern