Commit 865cfb8e authored by Marijn Suijten's avatar Marijn Suijten 🦀 Committed by Tim-Philipp Müller
Browse files

check: gst_test_clock_process_next_clock_id returns nullable

It is possible there are no more pending clocks in the chain, in which
case this function returns null.

See also tests like test_single_shot_async_future that validate NULL

Part-of: <!716>
parent 877f2b68
Pipeline #238967 waiting for manual action with stages
in 2 minutes and 10 seconds
......@@ -923,7 +923,7 @@ gst_test_clock_wait_for_pending_id_count (GstTestClock * test_clock,
* MT safe.
* Returns: (transfer full): a #GstClockID containing the next pending clock
* Returns: (transfer full) (nullable): a #GstClockID containing the next pending clock
* notification.
* Since: 1.2
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment