[Bug 761211] pad: blocking pull probe during pull_range doesn't work

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=761211

--- Comment #28 from Thiago Sousa Santos <thiagossantos at gmail.com> ---
commit 368ee8a336d0c868d81fdace54b24431a8b48cbf
Author: Thiago Santos <thiagoss at osg.samsung.com>
Date:   Thu Mar 24 17:34:20 2016 -0300

    pad: rework probe's hook_marshall function

    PUSH and PULL mode have opposite scenarios for IDLE and BLOCK
    probes.

    For PUSH it will BLOCK with some data type and IDLE won't have a type.
    For PULL it will BLOCK before getting some data and will be IDLE when
    some data is obtained.

    The check in hook_marshall was specific for PUSH mode and would cause
    PULL probes to fail to be called. Adding different checks for the mode
    to fix this issue.

    https://bugzilla.gnome.org/show_bug.cgi?id=761211

commit 1967d56aea6910b7ee238dda905b549a6be575af
Author: Thiago Santos <thiagoss at osg.samsung.com>
Date:   Thu Mar 24 17:34:40 2016 -0300

    tests: pad: extra tests for pad pull probes

    For BUFFER and IDLE probes

    https://bugzilla.gnome.org/show_bug.cgi?id=761211

commit a7813adb1d87e01b7746bb0b9dc822728a200eda
Author: Matej Knopp <matej.knopp at gmail.com>
Date:   Thu Jan 28 16:22:17 2016 +0100

    pad: Add test for blocking pull probe

    https://bugzilla.gnome.org/show_bug.cgi?id=761211

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.