After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 510974 - [GstSystemClock] test_periodic_shot:0: Waiting did not return OK
[GstSystemClock] test_periodic_shot:0: Waiting did not return OK
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-21 08:16 UTC by Sebastian Dröge (slomo)
Modified: 2009-02-03 13:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2008-01-21 08:16:58 UTC
Hi,
since 0.10.15.2/.3 the test_periodic_shot test sometimes fails, at least on amd64 and arm with "Waiting did not return OK".

This happened at least on the Debian build bots and Stefan had this too. We both suspect that the monotonic clocks patch is causing this, as nobody saw this before.
Comment 1 Tim-Philipp Müller 2008-01-21 10:00:19 UTC
I've seen this before, and I believe it was simply due to the machine being under heavy load.

See bug #440682.
Comment 2 Jan Schmidt 2008-01-21 17:26:59 UTC
That seems like the most likely cause given that it's intermittent. I can't reproduce it here, but it might be easier to trigger on a machine with a slower CPU, or a kernel with a lower HZ setting.

I don't think it's a blocker unless we can demonstrate conclusively that it's not just a race in the test.
Comment 3 Jan Schmidt 2008-01-21 20:10:17 UTC
In the absence of reproduceability, removing the blocker flag :)
Comment 4 Tobias Mueller 2009-01-23 01:36:53 UTC
Hey folks.

Any news on this one? It's set to NEEDINFO for quite some time now.
Comment 5 Tim-Philipp Müller 2009-02-03 13:31:10 UTC
Can't reproduce this any longer no matter how hard I try. Closing for now, please re-open if it's still an issue.