GNOME Bugzilla – Bug 440682
gst/gstsystemclock unit test occasionally fails
Last modified: 2007-05-24 15:03:37 UTC
Running suite(s): GstSystemClock 85%: Checks: 7, Failures: 1, Errors: 0 gst/gstsystemclock.c:239:F:waiting:test_async_order:0: Missing notification for id1 FAIL: gst/gstsystemclock Running suite(s): GstSystemClock 71%: Checks: 7, Failures: 2, Errors: 0 gst/gstsystemclock.c:179:F:waiting:test_periodic_shot:0: Waiting did not return OK gst/gstsystemclock.c:237:F:waiting:test_async_order:0: Expected notification for id2 to come first
Created attachment 88665 [details] gzipped debug log of ':waiting:test_periodic_shot:0: Waiting did not return OK' failure
Created attachment 88666 [details] gzipped debug log of 'test_async_order:0: Expected notification for id2 to come first' failure
Seems the deadline is missed (100ms) in the first case. increasing the TIME_UNIT might help to reduce this problem. We could also ignore GST_CLOCK_EARLY..
the second test could be written better, patch follows..
this patch should improve the test. * tests/check/gst/gstsystemclock.c: (store_callback), (GST_START_TEST): Improve test_async_order to also work when both timers are already expired when we get scheduled to check it.
FWIW, it works fine for me now. One of the tests still fails occasionally under high cpu load, but that's to be expected for timing-sensitive stuff, I guess. The order test always passes for me now.
Confirming that, too. The tests ran here for almost three hours on a calm CPU without a single failure now.