check: Add a debug status to the systemclock test

Next time it fails on a buildbot we can see which clock id
return it is getting.
This commit is contained in:
Jan Schmidt 2009-11-14 22:35:07 +00:00
parent 8c4742866b
commit 7a8fa2b6a0

View file

@ -395,7 +395,7 @@ GST_START_TEST (test_async_sync_interaction)
/* While this is sleeping, the async3 id should fire and unschedule it */ /* While this is sleeping, the async3 id should fire and unschedule it */
result = gst_clock_id_wait (td.sync_id, &jitter); result = gst_clock_id_wait (td.sync_id, &jitter);
fail_unless (result == GST_CLOCK_UNSCHEDULED || result == GST_CLOCK_EARLY, fail_unless (result == GST_CLOCK_UNSCHEDULED || result == GST_CLOCK_EARLY,
"Waiting did not return UNSCHEDULED"); "Waiting did not return UNSCHEDULED (was %d)", result);
gst_clock_id_unschedule (td.async_id3); gst_clock_id_unschedule (td.async_id3);
g_mutex_lock (td.lock); g_mutex_lock (td.lock);