superficial tests that pass are marked as neutral. In Debian's implementation, this means that a package that only has superficial autopkgtests will NOT get the autopkgtest "bounty" which reduces the number of days a package must wait in Unstable before automatically migrating to Testing. (The bounty is set to 3 so a typical upload will take 2 days instead of 5 days).
superficial tests that pass are marked as neutral. In Debian's implementation, this means that a package that only has superficial autopkgtests will NOT get the autopkgtest "bounty" which reduces the number of days a package must wait in Unstable before automatically migrating to Testing. (The bounty is set to 3 so a typical upload will take 2 days instead of 5 days).
https:/ /salsa. debian. org/ci- team/autopkgtes t/-/blob/ master/ doc/README. package- tests.rst
https:/ /salsa. debian. org/release- team/britney2/ -/blob/ master/ etc/britney. conf#L81
However, if a superficial autopkgtest fails, as happens with libwacom 2.9.0-1 , it must be treated as a failure.
A migration- reference/ 0 of neutral should not allow a failing autopkgtest to migrate.
As of today, libwacom is still not fixed and is only held in proposed by my block-proposed bug so I think this is a clear test case right now.