Source: bagel Version: 1.2.2-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky
Dear maintainer(s), With a recent upload of gcc-10 to unstable, the autopkgtest of bagel failed on arm64 in testing when that autopkgtest was run with the binary packages of gcc-10 from unstable. I looked into the history of your autopkgtest and it fails very often. 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. Please either fix the test to be more robust, or or use the "flaky" restriction for the offending test until a solution has been found. I copied the output at the bottom of this report. All the failing tests that I inspected look like it, albeit the test that fails differs between runs. I'll have the migration software ignore the results of your autopkgtest on arm64 until this bug is fixed. Paul https://ci.debian.net/data/autopkgtest/testing/arm64/b/bagel/4258642/log.gz running test case 'hf_sto3g_relfci_gaunt'... terminate called without an active exception /tmp/autopkgtest-lxc.q3t4znog/downtmp/build.F1y/src/debian/tests/testsuite.sh: line 85: 15487 Aborted BAGEL test/${testname}.json > ${testname}.out /tmp/autopkgtest-lxc.q3t4znog/downtmp/build.F1y/src/debian/tests/testsuite.sh: fork: retry: Resource temporarily unavailable FAILED.
signature.asc
Description: OpenPGP digital signature
