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 617418 - [tests] adder test_live_seeking is unreliable
[tests] adder test_live_seeking is unreliable
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-02 09:04 UTC by Edward Hervey
Modified: 2013-08-13 15:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Edward Hervey 2010-05-02 09:04:12 UTC 
This test seems to rely on alsasrc being able to output data when PLAYING.

The problem is that alsasrc could be preset AND responsive (there is a device), but not output anything in PLAYING. This seems to be the case with pulse audio systems (see f13 buildslave, also reproduceable on a freshly installed gentoo ~amd64 with pulseaudio/alsa).

Add to that the fact that adder silently discards FALSE seek requests from upstream (in this case alsasrc will return FALSE).
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2010-05-07 18:09:35 UTC 
I'll see if I can skip the test when using a broken alsasrc. Do you have any explanation for the alsasrc behaviour.

Please note that audiotestsrc is not behaving the same, even if is-live=true (maybe that should be improved instead).
Comment 2 Edward Hervey 2010-05-08 11:54:00 UTC 
Seems to be related to having alsa-over-pulseaudio setups (i.e. applications accessing the 'default' alsa device will end up going through pulseaudio) and I can see alsasrc ! fakesink connecting to pulseaudio in the Sound Preferences.

Now... the even weirder part... If I switch my Hardware setup from "Analog Stereo Duplex" to "Analog Stereo Output" (i.e. from having both input/output to only having output") ... it then works (!?!?!?)
Comment 3 Edward Hervey 2013-08-13 15:22:52 UTC 
Passes fine now. Closing.