Timo Aaltonen kirjoitti 12.1.2023 klo 20.57:
Paul Gevers kirjoitti 27.6.2022 klo 21.31:
Source: dogtag-pki
Version: 11.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it
was showing up on our "slow" page [1]. I noticed that there were
several runs that took 2:47 (our timeout time), while successful runs
more in the order of minutes.
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.
On top of that, when a test just hangs that's not good for our
infrastructure. I'll put dogtag-pki on our reject_list for amd64,
armhf, and s390x.
Don't hesitate to reach out if you need help and some more information
from our infrastructure. E.g. I note that the runs on amd64 that I
happen to check are run on ci-worker13 that, together with our armhf
worker is running on a host with lots of CPUs (64 and 160) and RAM
(256GB and 511GB) and also our s390x has 10 CPUs and 32 GB.
Paul
[1] https://ci.debian.net/status/slow/
Hi,
I've finally updated dogtag-pki to fix some grave bugs, but this still
remains. I don't know if the update fixes these racy tests (which they
are, something goes wrong and it gets stuck), but is there a way for me
to manually trigger them on ci.debian.net? They do pass on salsa-ci, but
it's not the same thing..
Looks like the tests are still being run, which at least shows that they
seem to be just as racy still :/ I need to reproduce the failure
locally, which has been impossible so far.
--
t
