Source: debci
Version: 4.4
Severity: serious
User: [email protected]
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package because it
was blocking curl. I noticed that it regularly fails on riscv64.
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/d/debci/testing/riscv64/77960727/
786s /var/tmp/autopkgtest.hG5YW0/tests-tree/test/test_worker.sh
2636s test_no_crash_success
2636s Error: operation wait on node
debci-rabbitmq-autopkgtest-incus-ltaqpm-qx2sno@autopkgtest-incus-ltaqpm
timed out. Timeout value used: 10000
2636s E: timed out after 60 seconds, waiting for rabbitmq-server to
start. The following tests will probably fail
2636s Terminated
2636s ASSERT:has leftover requests expected:<0> but was:<1>
2636s ls: cannot access
'/tmp/debci.data.N2WorE/data/autopkgtest/unstable/riscv64/m/mypkg/*/log.gz':
No such file or directory
https://ci.debian.net/packages/d/debci/testing/riscv64/77832652/
488s autopkgtest [09:33:04]: test test-suite: [-----------------------
489s /var/tmp/autopkgtest.snu3PY/tests-tree/test/test_worker.sh
3489s autopkgtest [10:23:05]: ERROR: No output received for 3000s