Hi Simon, On 24-08-2025 14:10, Simon Josefsson wrote:
I have triggered a bunch of jobs for some other archs too, but this appears to be amd64-specific:
Interesting. Our amd64 worker is the most powerful host that we have. Might it be a race condition, or something related to parallelism?
Paul, would the patch below improve the situation for you in Debian, or doesn't it matter until we stop making this test flaky?
Sure it does help on the infrastructure, but it does paper over the real problem.
I suppose we could remove the test from the debian/tests/ but I believe it actually indicate a serious upstream problem that we want to get resolved.
Are you talking about only this test, or the whole test stanza in d/t/control? In my opinion removing an individual test from a suite is better than marking a full stanza as flaky.
Btw, what is the workflow that ends up noticing about flaky test in guile-fibers? I would expect guile-fibers to not have any reverse build dependencies in Debian except for packages I work on.
I'm currently checking all packages where the last "pure" testing run in the last 2 months is failing. This includes flaky tests.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
