Bug#1051811: pytorch-vision: Failing autopkgtests

[Jeremy Bícha <jeremy.bicha@canonical.com>]

On Tue, Sep 12, 2023 at 6:08 PM Petter Reinholdtsen <pere@hungry.com> wrote:
> [Jeremy Bícha]
> > Autopkgtest failures currently prevent migration to Testing even when
> > the autopkgtests have never passed on an architecture.
>
> As far as I know, a test that never succeeded will not be considered a
> regression and will not block migration.
>
> <URL: https://tracker.debian.org/pkg/pytorch-vision > claim the failing
> ppc64el and s390x tests are regression.  Is this wrong?

If you click ppc64el (or any architecture) from that page, it shows
the test history. That test has only been run once on that
architecture and it failed.

Currently, Debian is set up to block migration even for this case.
That is why pytorch-vision has not migrated to Testing despite meeting
the 5 day wait.

Ubuntu's migration system does not block for an autopkgtest that never
succeeded but Debian's is stricter, perhaps to discourage autopkgtests
being run that never pass? Debian's autopkgtest system may have been
looser earlier but it has been this way for a while now.

Thank you,
Jeremy Bícha