On Wed, 28 May 2025 at 17:06:52 -0400, Richard Hansen wrote:
* What does "autopkgtest bounty" mean in the table at
<https://release.debian.org/testing/freeze_policy.html#summary>?
When we aren't in a freeze, packages with successful non-superficial
autopkgtests migrate sooner than packages with a "neutral" autopkgtest
result. That delay reduction is the "autopkgtest bounty".
If I remember correctly, urgency=medium normally migrates in 2 days
after a successful non-superficial autopkgtest, compared with 5 days if
there are no autopkgtests or if they are all superficial, skipped, or
failing-but-marked-flaky.
* If I add a non-superficial autopkgtest to a package that
currently does not have an autopkgtest, will it be eligible for
automatic migration to testing or do I have to request an unblock?
I don't know for sure, but I think probably it would be eligible for
automatic migration, if the test passes. But if the test fails (even
intermittently) then you've made things worse for this package, and for
other packages too; in your position I'd want to add this test coverage
in experimental first, and delay adding it in unstable until the forky
cycle opens unless there's a reason why it's particularly important.
Context: I'm wondering if it makes sense to merge
<https://salsa.debian.org/debian/keyd/-/merge_requests/4> or if that
would just complicate the process of unblocking it.
I see you're adding a bunch of superficial tests, plus a non-superficial
test that needs isolation-machine. I think you would need to ask for manual
action before this will give you meaningful test coverage: ci.debian.net
normally runs tests in autopkgtest-virt-lxc, which only provides
isolation-container and not isolation-machine. The CI team can allowlist
packages that benefit from it to run in autopkgtest-virt-qemu on amd64
(flatpak and bubblewrap are examples) but as far as I'm aware it isn't
automatic.
On architectures that test under autopkgtest-virt-lxc, or until the
package has been configured to use autopkgtest-virt-qemu, the best you
can hope for is the "neutral" status: the test that needs
isolation-machine will be skipped, and the rest are superficial.
smcv
