The latency messages are non-deterministic and can arrive before/after async-done or during state-changes as they are posted by e.g. sinks from their streaming thread but bins are finishing asynchronous state changes from a secondary helper thread. To solve this, expect latency messages at any time and assert that we receive one at some point during the test. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2643>
This directory contains regression tests, functionality tests, examples, benchmarks, ... benchmarks/ benchmarks to profile pieces of GStreamer check/ unit tests using the check library, non-interactive examples/ small examples demonstrating the use of various features misc/ prototypes, random bits, ...