On Tue, 11 Mar 2025 at 09:54:23 +0100, Francesco Poli wrote:
the DebCI [summary] page for apt-listbugs still shows
several failed tests and no results for apt-listbugs/0.1.47:
[...]
| unstable testing stable oldstable
| amd64 0.1.46 fail 0.1.46 fail 0.1.40 pass 0.1.35 pass
| arm64 0.1.45 pass 0.1.46 fail 0.1.40 pass 0.1.35 pass
| armel 0.1.46 pass 0.1.46 fail 0.1.40 pass 0.1.35 pass
| armhf 0.1.46 fail 0.1.46 fail 0.1.40 pass 0.1.35 pass
| i386 0.1.46 fail 0.1.46 fail 0.1.40 pass 0.1.35 pass
| loong64 0.1.45 pass No reference No reference No reference
| ppc64el 0.1.46 fail 0.1.46 fail 0.1.40 pass 0.1.35 pass
| riscv64 0.1.44 fail 0.1.45 pass No reference No reference
| s390x 0.1.45 pass 0.1.46 fail 0.1.40 pass 0.1.35 pass
[...]
[summary]: <https://ci.debian.net/packages/a/apt-listbugs/>
And the package [tracker] page still complains about failed Debci tests:
[...]
| Debci reports failed tests
[...]
[tracker]: <https://tracker.debian.org/pkg/apt-listbugs>
When will these failed test results be replaced by the passed test
results for apt-listbugs/0.1.47 ?
That will happen when ci.debian.net gets far enough through its queue to
have done a test that consists purely of packages from unstable or
testing (as appropriate) and includes apt-listbugs/0.1.47. (It will be
labelled "migration-reference".)
Most of the test runs that happen on ci.debian.net are not purely
unstable or purely testing: they're testing a hypothetical future state
of the distribution. For example the first job in
https://ci.debian.net/packages/a/apt-listbugs/testing/amd64/ at the time
of writing says:
Version: 0.1.47
Trigger/Pinned packages: apt/2.9.32 src:apt from unstable
That's testing a hypothetical future state of testing - "if apt/2.9.32
was allowed to migrate to testing, would apt-listbugs still pass its
tests?" - and in this case the answer is yes it would.
Similarly the majority of the test runs in unstable are actually
unstable + selected packages from experimental, to give maintainers a
preview of what would happen if they uploaded their packages in
experimental to unstable.
There has been no migration-reference job run in testing since 0.1.47
migrated, and it is the migration-reference jobs that are shown in the
summary.
smcv
