Bug#1023629: glib2.0: flaky autopkgtest on armhf and armel (on ci.d.n infra): glib/threadtests.test times out after 300 seconds
Control: clone -1 -2 Control: severity -2 important Control: retitle -2 glib2.0: gobject/tests/threadtests.c can take more than 5 minutes on armhf, armel On Mon, 07 Nov 2022 at 21:51:05 +0100, Paul Gevers wrote: > # Executing: glib/threadtests.test > # Executing: glib/threadtests.test > # Executing: glib/threadtests.test > not ok - Test timed out after 300 seconds > # FAIL: glib/threadtests.test (Child process killed by signal 9) For now, I'm going to move this test to the "flaky" set that is only run when a specific environment variable is set. As far as I can tell, it's working correctly, and it usually takes about 10-15 seconds and passes; but it intermittently takes more than 5 minutes, which is a timeout when running under ginsttest-runner. I don't know whether it would have passed if allowed more time, or whether it has deadlocked. I'm cloning a bug for the underlying test failure, so we have something to represent the failure mode even after the autopkgtest failure has been avoided. smcv
Bug#1023629: glib2.0: flaky autopkgtest on armhf and armel (on ci.d.n infra): glib/threadtests.test times out after 300 seconds
Source: glib2.0 Version: 2.74.0-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails since around March 2022 on armel [1] and the first of October 2022 on armhf [2]. 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 [1] https://ci.debian.net/packages/g/glib2.0/testing/armel/ [2] https://ci.debian.net/packages/g/glib2.0/testing/armhf/ https://ci.debian.net/data/autopkgtest/testing/armhf/g/glib2.0/26345811/log.gz # Executing: glib/threadtests.test # Executing: glib/threadtests.test # Executing: glib/threadtests.test not ok - Test timed out after 300 seconds # FAIL: glib/threadtests.test (Child process killed by signal 9) not ok - glib/threadtests.test [...] # SUMMARY: total=275; passed=272; skipped=2; failed=1; user=1680.6s; system=176.1s; maxrss=154072 # FAIL: glib/threadtests.test (Child process killed by signal 9) https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27696626/log.gz not ok - Test timed out after 300 seconds # FAIL: glib/threadtests.test (Child process killed by signal 9) not ok - glib/threadtests.test # Running test: glib/gutils-user-database.test # random seed: R02Sa857e7d4f9a0241ca5d1865ccc7eafc1 1..1 # Start of gutils tests ok 1 /gutils/get_user_database_entry # End of gutils tests ok - glib/gutils-user-database.test # SUMMARY: total=284; passed=281; skipped=2; failed=1; user=1566.6s; system=169.8s; maxrss=153428 # FAIL: glib/threadtests.test (Child process killed by signal 9) https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27421159/log.gz # SUMMARY: total=276; passed=273; skipped=2; failed=1; user=1555.8s; system=175.9s; maxrss=170864 # FAIL: glib/threadtests.test (Child process killed by signal 9) https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27116770/log.gz # SUMMARY: total=276; passed=273; skipped=2; failed=1; user=1552.2s; system=274.3s; maxrss=226436 # FAIL: glib/threadtests.test (Child process killed by signal 9) OpenPGP_signature Description: OpenPGP digital signature
