mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-19 16:21:17 +00:00
3537ad8ae1
The check itself is racy. (CK_FORK=no GST_CHECK=test_output_order make elements/multiqueue.forever). The problem is indeed the test and not the actual element behaviour. The objects to push are being pulled out of the single internal queues in the right order and at the right time... But between: * the moment the global multiqueue lock is released (which was used to detect if we should pop and push downstream the next buffer) * and the moment it is received by the source pad (which does the check) => another single queue (like the unlinked pad) might pop and push a buffer downstream What should we do ? Putting a bigger margin of error (say 5 buffers) doesn't help, it'll eventually fail. I can't see how we can detect this reliably. https://bugzilla.gnome.org/show_bug.cgi?id=708661 |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| check | ||
| examples | ||
| misc | ||
| .gitignore | ||
| Makefile.am | ||
| README | ||
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, ...