Source: autopkgtest Version: 5.33 Severity: serious User: debian...@lists.debian.org Usertags: flaky
Dear maintainer(s),I looked at the results of the autopkgtest of your package. I noticed that it recently started to fail a lot on ppc64el. The failures seem related to the host that runs the test. Several weeks ago, we commissioned a new host (ci-worker-ppc64el-05) with more cores, more RAM and faster disk and most recent tests ran on that host. Apart from the hardware, we also use /tmp on tmpfs (with lots of swap). Overall, I expect the host to be *faster* than the old hosts, but ironically the tests that seems to fail is: __main__.SchrootRunner.test_copy_timeout. As also amd64 has /tmp on tmpfs, I don't immediately suspect that to be the problem; also at least one run on ci-worker-ppc64el-05 passed (44524634).
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. Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
