Vincent Penquerc'h a3b42ec42a bin: undo upward state changes on children when a child fails ... When a bin changes states upwards, and a child fails to change, any child that was already switched will not be reset to its original state, leaving its state inconsistent with the bin, which does not change state due to the failure. If the state change was from NULL to READY, it means that deleting this bin will cause those children to be deleted while not in NULL state, which is a Bad Thing. For other upward changes, it is less of a problem, as a subsequent switch back to NULL will cause an actual downwards change on those inconsistent elements, albeit from the "wrong" state. We now reset state to the original one when a child fails. Includes unit test. https://bugzilla.gnome.org/show_bug.cgi?id=747610		2015-04-15 16:00:21 +01:00
..
elements	tests: multiqueue: add test to make sure initial events go through without buffers	2015-04-05 16:47:26 +01:00
generic	bin: undo upward state changes on children when a child fails	2015-04-15 16:00:21 +01:00
gst	tests: clock: fix test clock name	2015-04-15 09:31:11 +01:00
libs	baseparse: only post 'no valid frames' error if buffers were received	2015-03-26 12:25:57 -03:00
pipelines	Fix double semicolons	2015-03-10 09:24:28 +00:00
tools	tests: refactor tools check a little	2014-10-31 16:10:01 +00:00
.gitignore	tests: add check for gst-inspect --exists functionality	2012-09-01 23:02:10 +01:00
Makefile.am	tests: Use AM_TESTS_ENVIRONMENT	2015-04-08 16:08:24 +02:00