Skip to content

tests: Remove racy test to check ordering of sync/async clock callbacks

To check the logic the test required the OS to schedule the async callback within 30ms, which we have no guarantee is true.

We already have a GstTestClock test which checks the logic in a system independent manner (test_single_shot_sync_unschedule).

Merge request reports