El 24/1/25 a las 12:30, Luca Boccassi escribió:
Source: mutter
Version: 47.4-1
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainers,
mutter autopkgtest are flaky and often fail and require multiple
manual reruns to let unrelated packages migrate, especially on
armhf/armel/ppc64el. As per RT, this kind of bug is RC.
Please consider either fixing those tests, or marking them with
Restrictions: flaky so that failures do not affect other packages.
Thanks a lot for filing this bug.
More to the point:
This package FTBFS for me 20% of the time on AWS machines with 2 CPUs
and *100%* of the time on AWS machines with 1 CPUs, because of failing
tests.
Does this mean that the package will not work ok in such machines?
No, I don't really think so. I think the tests are just low quality
and not to be trusted a lot.
Therefore, when considering to mark one or more tests as flaky,
please do so in an "agnostic way", i.e. not by using the flaky keyword
in restrictions field, but preferably in a way which also benefits
people trying to build the package outside buildd.debian.org.
Thanks.
