Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
Hi Adrian, On 09-01-2021 21:37, Adrian Bunk wrote: > you are saying the version in unstable passes all tests for migration, > and needs only this bug closed? Yes. Otherwise the excuses would have mentioned the issues. Looking at the excuses_yaml I see this: - 'Migration status for bagel (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression' - 'Issues preventing migration:' - 'Updating bagel introduces new bugs: https://bugs.debian.org/952463";>#952463' - 'Additional info:' - Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bagel.html";>https://piuparts.debian.org/sid/source/b/bagel.html - Required age reduced by 3 days because of autopkgtest - 740 days old (needed 2 days) is-candidate: false item-name: bagel maintainer: Debichem Team migration-policy-verdict: REJECTED_PERMANENTLY new-version: 1.2.2-1 old-version: '-' policy_info: age: age-requirement: 2 current-age: 740 verdict: PASS autopkgtest: bagel/1.2.2-1: amd64: - PASS - https://ci.debian.net/data/autopkgtest/testing/amd64/b/bagel/4806582/log.gz - https://ci.debian.net/packages/b/bagel/testing/amd64 - null - null arm64: - PASS - https://ci.debian.net/data/autopkgtest/testing/arm64/b/bagel/5589842/log.gz - https://ci.debian.net/packages/b/bagel/testing/arm64 - null - null ppc64el: - PASS - https://ci.debian.net/data/autopkgtest/testing/ppc64el/b/bagel/7273182/log.gz - https://ci.debian.net/packages/b/bagel/testing/ppc64el - null - null verdict: PASS block: verdict: PASS build-depends: verdict: PASS built-using: verdict: PASS builtonbuildd: signed-by: amd64: buildd_amd64-x86-conova...@buildd.debian.org arm64: buildd_arm64-arm-ubc...@buildd.debian.org mips64el: buildd_mips64el-mipsel-manda...@buildd.debian.org ppc64el: buildd_ppc64el-ppc64el-unicamp...@buildd.debian.org s390x: buildd_s390x-zando...@buildd.debian.org verdict: PASS depends: verdict: PASS implicit-deps: verdict: PASS piuparts: piuparts-test-url: https://piuparts.debian.org/sid/source/b/bagel.html test-results: pass verdict: PASS rc-bugs: shared-bugs: [] unique-source-bugs: - '952463' unique-target-bugs: [] verdict: REJECTED_PERMANENTLY reason: [] source: bagel So it's only held back because of the bug. > At least I am not seeing any problem that has been observed during the > past 8 months that needs action. Paul PS: I did have a hint in place, but that was only to ignore failures on arm64. I've removed that just now. OpenPGP_signature Description: OpenPGP digital signature
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
On Sat, Jan 09, 2021 at 09:25:56PM +0100, Paul Gevers wrote: > Hi Adrian, Hi Paul, > On 09-01-2021 20:45, Adrian Bunk wrote: > > Considering the fact that noone ever understood what the problem was, > > could you re-enable the autopkgtest to see whether any problems are > > still present? > > Why do you think it's disabled (it's not AFAICT)? you are saying the version in unstable passes all tests for migration, and needs only this bug closed? At least I am not seeing any problem that has been observed during the past 8 months that needs action. > Paul cu Adrian
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
Hi Adrian, On 09-01-2021 20:45, Adrian Bunk wrote: > Considering the fact that noone ever understood what the problem was, > could you re-enable the autopkgtest to see whether any problems are > still present? Why do you think it's disabled (it's not AFAICT)? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
On Thu, Mar 19, 2020 at 10:16:32AM +0100, Paul Gevers wrote: >... > On 25-02-2020 15:56, Michael Banck wrote: >... > > On Mon, Feb 24, 2020 at 08:57:40PM +0100, Paul Gevers wrote: > >> 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. > > > > This looks like the arm64 authobuilder has not enough memory or > > something? > > autopkgtest don't run on the autobuilders, but I the message is of > course still relevant. The arm64 workers have plenty of memory, so if > the memory is exhausted, the test should implement a check and fail > gracefully if there isn't enough to run the test. Interestingly, in the > logs I check I see different tests and different amount of tests fail. > Are the tests run in parallel? Could this be turned off (at least to see > if things become more stable) or the amount of parallelism be reduced? The results from accidental builds in recent months look good: https://ci.debian.net/packages/b/bagel/unstable/arm64/ Considering the fact that noone ever understood what the problem was, could you re-enable the autopkgtest to see whether any problems are still present? > Side note which warrants it's own bug; bagel (at least the autopkgtest) > needs an update due to the new mpich (seen both on arm64 and amd64): > running test case 'hf_sto3g_relfci_coulomb'... BAGEL: error while > loading shared libraries: libmpichcxx.so.12: cannot open shared object > file: No such file or directory >... This was a bug in libmpich12 that was fixed/reverted in April. > Paul cu Adrian
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
Hi Michael, On 25-02-2020 15:56, Michael Banck wrote: > Hi Paul, > > On Mon, Feb 24, 2020 at 08:57:40PM +0100, Paul Gevers wrote: >> 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. > > This looks like the arm64 authobuilder has not enough memory or > something? autopkgtest don't run on the autobuilders, but I the message is of course still relevant. The arm64 workers have plenty of memory, so if the memory is exhausted, the test should implement a check and fail gracefully if there isn't enough to run the test. Interestingly, in the logs I check I see different tests and different amount of tests fail. Are the tests run in parallel? Could this be turned off (at least to see if things become more stable) or the amount of parallelism be reduced? Side note which warrants it's own bug; bagel (at least the autopkgtest) needs an update due to the new mpich (seen both on arm64 and amd64): running test case 'hf_sto3g_relfci_coulomb'... BAGEL: error while loading shared libraries: libmpichcxx.so.12: cannot open shared object file: No such file or directory FAILED. running test case 'hf_sto3g_relfci_gaunt'... BAGEL: error while loading shared libraries: libmpichcxx.so.12: cannot open shared object file: No such file or directory FAILED. running test case 'hf_sto3g_relfci_breit'... BAGEL: error while loading shared libraries: libmpichcxx.so.12: cannot open shared object file: No such file or directory FAILED. Paul signature.asc Description: OpenPGP digital signature
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
Hi Paul, On Mon, Feb 24, 2020 at 08:57:40PM +0100, Paul Gevers wrote: > 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. This looks like the arm64 authobuilder has not enough memory or something? Michael
Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
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