Thanks for the report! Here is my analysis, mostly intended as reference for a future upstream bug report.
List of all debci jobs: https://ci.debian.net/packages/g/guile-fibers/testing/amd64/ Click on the 'test log' link in the 'Results' column for those lines where 'Status' indicate 'fail'. I have triggered a bunch of jobs for some other archs too, but this appears to be amd64-specific: https://ci.debian.net/packages/g/guile-fibers/testing/arm64/ https://ci.debian.net/packages/g/guile-fibers/testing/ppc64el/ https://ci.debian.net/packages/g/guile-fibers/testing/riscv64/ https://ci.debian.net/packages/g/guile-fibers/testing/s390x/ I have seen these failures myself earlier, but they usually just disappear when I try to debug it, and buildds and Salsa CI is more often happy than debci is, for some reason. Reviewing the failures, it seems all of them are 'guile-tests-basic' which is: Test-Command: guile tests/basic.scm Features: test-name=guile-tests-basic, Restrictions: allow-stderr, Depends: guile-3.0, guile-fibers, The failures all fail before <5 minutes, so there are no infloops or long delays here. They all also fail on exactly the same line: assert terminates: (run-fibers (lambda () (spawn-fiber-chain 5000)) #:drain? #t): Aborted Paul, would the patch below improve the situation for you in Debian, or doesn't it matter until we stop making this test flaky? 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. 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. /Simon diff --git a/debian/tests/control b/debian/tests/control index 248e3da..d5d09cb 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -3,6 +3,7 @@ Features: test-name=guile-tests-basic, Restrictions: allow-stderr, + flaky, Depends: guile-3.0, guile-fibers, Paul Gevers <[email protected]> writes: > Source: guile-fibers > Version: 1.3.1-7 > Severity: serious > User: [email protected] > Usertags: flaky > > Dear maintainer(s), > > I looked at the results of the autopkgtest of your package. I noticed > that it regularly fails. I scheduled 10 tests yesterday in testing on > amd64 and it failed 8 times. I've put some of the output of one of the > failures below, but it seems like the failures are not always the same > (across architectures). > > 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 > > https://ci.debian.net/packages/g/guile-fibers/testing/amd64/63640034/ > > 129s assert terminates: (run-fibers (lambda () (spawn-fiber-chain 50)) > #:drain? #t): ok (0.206824881 s) > 129s assert terminates: (run-fibers (lambda () (spawn-fiber-chain > 500)) #:drain? #t): ok (0.166856084 s) > 130s assert terminates: (run-fibers (lambda () (spawn-fiber-chain > 5000)) #:drain? #t): Aborted > 130s autopkgtest [14:37:45]: test guile-tests-basic: > -----------------------] >
signature.asc
Description: PGP signature
