Paul Gevers <[email protected]> writes: > I looked at the results of the autopkgtest of your package. I noticed > that it regularly fails on some architectures, particularly on s390x, > but not exclusively there. Yesterday I triggered 5 or 6 reference runs > on every architecture and 6/6 failed on s390x and 1/5 failed on > ppc64el. The error message suggests the solution is to turn deadlines > off. Can you consider doing that? The same error happened at least > once also on amd64, so it's not only the "obscure" release > architectures. > > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between > passing and failing without changes to the list of installed packages, > are causing people unrelated to your package to spend time on these > tests. > > Don't hesitate to reach out if you need help and some more information > from our infrastructure.
Thanks a lot for this report. I am making an upload with a patch that bumps the test deadline by an order of magnitude. That seems to fix the flakiness, as far as I can tell. But of course, this failure wasn't 100% reproducible, so please don't hesitate to reopen if the problem persists. Best, Gard
signature.asc
Description: PGP signature
