[Bug 752498] GstHarness improvements

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Thu Jul 16 09:10:07 PDT 2015


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

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.5.3

--- Comment #2 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
commit 0841b2a97ed031edc3c9d221fdf77ac7f0020b43
Author: Havard Graff <havard.graff at gmail.com>
Date:   Thu Jul 16 17:53:40 2015 +0200

    harness: don't re-establish the harness sink and src pads

    Given that the element has the possibility to have one, they should
    already be there.

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

commit 8597284d0be697bffbdb9f31a0f4e6576bc0a73f
Author: Stian Selnes <stian at pexip.com>
Date:   Mon Jul 13 11:03:13 2015 +0200

    harness: Improve detection of element type

    The element flag does not indicate wether a bin should be tested as a
    source or as a sink, eg. a bin with the sink flag may still have a
    source pad and a bin with the source flag may have a sink pad. In this
    case it is better to determine the element type by looking at the
    available pads and pad templates.

    Also rename srcpad and sinkpad where it actually represents
    element_srcpad_name and element_sinkpad_name.

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

commit fe6f694dbb7f64a37a7db7dd095da75a628645ca
Author: Stian Selnes <stian at pexip.com>
Date:   Mon Jul 13 11:10:49 2015 +0200

    harness: Forward sticky events to sink harness

    Fixes issue where if a sink harness was added late the sticky events
    would not be forwared.

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

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


More information about the gstreamer-bugs mailing list