After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609486 - [multiqueue] unit test fails after recent changes
[multiqueue] unit test fails after recent changes
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.29
Other Linux
: Normal critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-10 01:34 UTC by Tim-Philipp Müller
Modified: 2010-10-27 11:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2010-02-10 01:34:15 UTC
Needs investigating/confirming that it's really the test's fault. Seems racy here.
Comment 1 Edward Hervey 2010-02-10 13:48:35 UTC
commit 5a0cdc700159582ad904272bd4daa2d31a36422c
Author: Edward Hervey <bilboed@bilboed.com>
Date:   Wed Feb 10 14:40:17 2010 +0100

    tests: Fix multiqueue test for latest commits.
    
    The problem lies in the fact that multiqueue will now operate somewhat
    similarly to the flow aggregation logic of demuxers and therefore
    will stopp whenever all downstream pads return NOT_LINKED and/or
    UNEXPECTED and there's no more buffers to push.
    
    The latest commits should not affect any regular use-case, but the bug
    report will be kept open so the previous behaviour can be re-established
    if needed.
    
    Fixes #609486
Comment 2 Sebastian Dröge (slomo) 2010-02-25 17:05:47 UTC
Any news on this blocker?
Comment 3 Tim-Philipp Müller 2010-02-25 17:17:49 UTC
I don't think it's a genuine blocker, and it's really too late in the cycle to touch this stuff now anyway, unless it turns out it actually causes problems, so removing blocker status.
Comment 4 Jan Schmidt 2010-10-27 11:13:27 UTC
Pretty sure this can be closed after 8 months of testing :)