Your message dated Tue, 15 Mar 2022 12:04:39 +0000 with message-id <e1nu5up-00013p...@fasolo.debian.org> and subject line Bug#1001801: fixed in dogtag-pki 11.0.3-1 has caused the Debian Bug report #1001801, regarding dogtag-pki: hits autopkgtest timeout on powerful workers to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1001801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: dogtag-pk Version: 11.0.0-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@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/OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Source: dogtag-pki Source-Version: 11.0.3-1 Done: Timo Aaltonen <tjaal...@debian.org> We believe that the bug you reported is fixed in the latest version of dogtag-pki, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen <tjaal...@debian.org> (supplier of updated dogtag-pki package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 15 Mar 2022 13:21:56 +0200 Source: dogtag-pki Built-For-Profiles: noudeb Architecture: source Version: 11.0.3-1 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team <pkg-freeipa-de...@alioth-lists.debian.net> Changed-By: Timo Aaltonen <tjaal...@debian.org> Closes: 1001801 Changes: dogtag-pki (11.0.3-1) unstable; urgency=medium . * New upstream release. * defauilt-webapp-timeout.diff: Force default webapp start timeout to 120 seconds. (Closes: #1001801) * tests: Dump selftests.log if pkispawn fails, and also drop dumping pkispawn log since we have --debug now. Checksums-Sha1: 589930f5e6fcdfb36ceb2f5b015d06e0cc3ac0eb 3789 dogtag-pki_11.0.3-1.dsc 2168bc78ca771abf997226ba379c148cf9ce4046 6846448 dogtag-pki_11.0.3.orig.tar.xz 5f4d7edaae49ba94459235d8734e5fab8cfa2428 42860 dogtag-pki_11.0.3-1.debian.tar.xz 2e23e85ac49145b34093a668d1811f13ac4d369c 13254 dogtag-pki_11.0.3-1_source.buildinfo Checksums-Sha256: ceb97eeace955f765bdbcf4745d01bbf7050ad073cad1dc51f3c5d81fd5d0335 3789 dogtag-pki_11.0.3-1.dsc 1e342a149926911142945a5df8a3ae02f3807c201e67843dbeb3e56a2fbf34d1 6846448 dogtag-pki_11.0.3.orig.tar.xz f4f81d39ef48228a29097158f6dc6cf40f5aa0cb7367ebb7b3ebdeabb5d87b44 42860 dogtag-pki_11.0.3-1.debian.tar.xz 3eaa1365c4d1baa02981484fa43c67c0e26714b65023334ef02cdcbc1cf585f9 13254 dogtag-pki_11.0.3-1_source.buildinfo Files: 7a3dec18a6e305f8c40ac97ec876295c 3789 java optional dogtag-pki_11.0.3-1.dsc 5a083abf0dccd7a928571edbd88ad21c 6846448 java optional dogtag-pki_11.0.3.orig.tar.xz 7caf20ca6d6900eeb96fb710c4858040 42860 java optional dogtag-pki_11.0.3-1.debian.tar.xz 10b8747162633f685c6bc2c09b8bc849 13254 java optional dogtag-pki_11.0.3-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmIwd3QACgkQy3AxZaiJ hNxdPg/+OoYTZW9ilrzt2ZMEYaWoQEsmPDBmrxfUDR6nmJKWFUUngO7nkQSGhvuO rut1vB4jFRkFdc1/BLvxAVBeR9pcGmHp58bxyLSyjtBoRs2UCbMbFY0Yrnn1kHaE +w9sHyHAZUS6o2vV9RHFObp+c59hFZ7Fxiewb9yuV1tSiV58KELi96ausgA1Vlvy CHEK5lS8QeITGmApK24bL7VNZJzNx0HOB4ReamYyWuKB5JPC7ohOfrdaqtWgpeLY vDV8BS3BSwuL/KhiZhugCh4aqKFgnoQSdOKCVZtR/j2sy2tqiPN73nBV/aC8A7wp WWKXsbbZNnFVvTdydI2gWuKFTeyRgQsRykEAqMInt4KWW6GooJgYiUc8NqzhcPeD MMPSvKPGLkWsLI5hxKSzo1OzH8OV1vSYky47o3PYRMIgxJ9BF/xexvinRk8cBk4x rl5J4wHJzyPnEsEDtpafwHZNoRKNpFR3pchEdGBwsdJfAUGC5W0PUuoiX/VXjKlm hlWSe9oTsCLmjMkgI2GSvAPXV48IDEINIuTM534mP6g6ZyUiuFSuZgx0ylY0wSCT wLNxnb/EWiYsbtOv4sSl8rteTeOfGQMlnJPHbNUMyPWnZ6rNPhP7ubfkgmHzwsX3 Ckv3InABgbfaDoHAd9atGxbSAAzumxf+omQnihN2JNBQMoHr1EQ= =DZeF -----END PGP SIGNATURE-----
--- End Message ---