WIP: tests: remove queues introducing raciness in flvmux test
GST_CHECKS=test_incrementing_timestamps meson test elements_flvmux
-C build --repeat 10000
Unexpected critical/warning: gst_clock_id_unref: assertion 'id != NULL' failed
What I observed is that between the call to test_clock_wait_next_pending_id and test_clock_process_next_id, the clock entry was unscheduled by gst_aggregator_pad_chain_internal.
Removing the queues before flvmux preserve the intention of the test, but makes it deterministic by making sure buffers are pushed on the test thread.
I can also observe a SIGSEGV every once in a while but it doesn't seem related.