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
