Source: dogtag-pk Version: 11.0.0-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian-ci@lists.debian.org User: debian-ci@lists.debian.org Usertags: flaky timeout Dear maintainer(s), Your package has an autopkgtest, great. However, because of some failure"caused" by another package, I looked into the history of your autopkgtest [1] and I noticed it fails regularly on amd64 and armhf because it hits the autopkgtest timeout after 2:47 hours.
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.In this case I noticed that at least the failures on amd64 that I looked at all happened on ci-worker13, which is our 48 core, 256 GB machine, while the test on other amd64 workers passed (as far as I checked). Similar, our armhf worker is also powerful: 160 core, 255 GB. Is there anything in the test that you can think of that can't handle so much resources?
The last entry in one of the amd64 logs is this (maybe add at least a timeout on calls like that):
INFO: Creating /etc/pki/pki-tomcat/Catalina/localhost/kra.xml INFO: Waiting for web application to startIf you need help to investigate this on the workers in question, don't hesitate to reach out.
Paul [1] https://ci.debian.net/packages/d/dogtag-pki/
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature