Please support Build-Profiles to select which tests should be run.  On
ci.debian.net the test runs would just use the empty list, like buildds
do as well.

The linux package currently generates a lot of tests, for every
combination of kernels it could build.  Not all of those packages are
built for the Debian archive, but only for CI use, aka they are disabled
by this in the debian/control stanza:
| Build-Profiles: <pkg.linux.quick>

Right now the autopkgtest definition relies on skip-not-installable to
allow skipping tests for packages that are not build.  I understand this
as a hack, so a proper replacement would be nice.  (This, and selection
by architecture.)

Hi waldi,


If your aim is to have tests that you can run locally but want to avoid
"downstream" than you can do that already (and I recall some package do
that already) by adding a unsupported restriction to those tests: those
are skipped by default. Running locally you can then force autopkgtest
to run those tests despite the restriction with --ignore-restrictions
(see the man page).

Does this cover your use case?

Paul

Nope.  The set of packages in both cases are not a superset of the other,
they are disjunct.  So it really needs a selection mechanism.

Bastian