Skip to content

validate: scenario: Mark seek as done only when reaching next state

Thibault Saunier requested to merge thiblahute/gst-devtools:wait_change_state into master 
commit be36e8369c07d3a15eae8882fd0903c62ea866ca (HEAD -> wait_change_state, thiblahute/wait_change_state)
Author: Thibault Saunier <tsaunier@igalia.com>
Date:   Thu May 14 19:22:18 2020 -0400

    scenario: Minor cleanup around pipeline change state management

commit 3743fb09338dd3621fdefea8c18a2470cd506749
Author: Thibault Saunier <tsaunier@igalia.com>
Date:   Thu May 14 18:45:11 2020 -0400

    scenario: Mark seek as done only when reaching next state
    
    There is a race where following actions could generate a
    flush-start/flush-stop dance but the state change resulting from the
    seek hasn't been committed yet, leading to the ASYNC_START being
    ignored by GstBin since its pending_state is not VOID when receiving
    the ASYNC_START message.
    
    Conceptually it is totally correct to consider an action done when
    the state change of the pipeline is stabilized..
Edited by Thibault Saunier

Merge request reports