Hi Peter,These questions are better addressed at the Release Team, who is responsible for the rules of migration. The Debian CI team merely offers infrastructure to run autopkgtests.
On 08-02-2023 04:03, Peter Colberg wrote:
For a package in unstable that has reached an age of 5 days and otherwise satisfies migration requirements, does a single pending autopkgtest block migration or add a penalty to the age [1, 2]? > [1] https://wiki.debian.org/ContinuousIntegration/DebianSetup [2] https://release.debian.org/doc/britney/solutions-to-common-policy-issues.html#britney-complains-about-autopkgtest
It blocks migration.
I am waiting for two dependent packages [3, 4] to reenter testing before the soft freeze, and while autopkgtest were run on other architectures after acceptance into the archive, s390x has been stuck at "Test in progress" with a queue [5] spanning 7 days. Will that block re-entrance when the packages reach an age of 5 days?
The tests in the queue have different priorities. There's tests that are scheduled for security uploads, they get highest prio as do tests that are scheduled by humans (by default). Test for migration testing are in the middle. The biggest chuck is migration-reference/0 runs scheduled by a cron job of mine, they are at the very bottom of priority.
[3] https://tracker.debian.org/pkg/acmetool [4] https://tracker.debian.org/pkg/golang-gopkg-hlandau-service.v2 [5] https://ci.debian.net/status/pending/?arch%5B%5D=s390x
> For instance, cacti [6] 1.2.23+ds1-2 was accepted on 2023-01-19 and > migrated to testing on 2023-01-21, but has not passed autopkgtest on > ppc64el and s390x to date.Your confusing testing and unstable. For migration, there's a special job triggered with testing as base suite, with a very limited set of packages (ideal only the candidate) added from unstable. Those were run for cacti and succeeded.
> There are two pending, migration-reference > jobs for these archs [7], submitted on 2023-02-01 and 2023-02-07. > > [6] https://tracker.debian.org/pkg/cacti > [7] https://ci.debian.net/packages/c/cacti/What you see at [7] doesn't show what was used for migration. The "front" page only shows "pure" runs, while the migration runs are mixed. We have a long standing desire to improve that front page to make that more clear, but we also fail to find a good design.
> It appears that pending autopkgtest do not delay migration to testing. They do delay unless overwritten by the Release Team. Paul PS: the s390x problem has resolved itself for now.
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature