Re: Bug#1023652: glib2.0: gobject/tests/threadtests.c can take more than 5 minutes on armhf, armel
Control: tags -1 + help
On Tue, 08 Nov 2022 at 09:47:15 +0000, Simon McVittie wrote:
> 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 took this out of the "flaky" set in the hope that it had been fixed
upstream, but it seems that wasn't true. For the next upload I'm going to
reinstate that.
The failing test-case appears to be specifically
test_threaded_toggle_notify().
This particular test has never been fully reliable, especially on
32-bit ARM. This might indicate a real problem, or it might be a quirk
of ARM specifically. If you are interested in making this more reliable,
please talk to GLib upstream.
Thanks,
smcv
Reply to: