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 517350 - gst-python tests fail on Solaris
gst-python tests fail on Solaris
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-python
git master
Other opensolaris
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-19 00:32 UTC by Brian Cameron
Modified: 2010-05-11 09:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Brian Cameron 2008-02-19 00:32:59 UTC
In the testsuite directory, I run "make check", and I see these errors

----

Traceback (most recent call last):
  • File "/export/home/brianca/packages/BUILD/gst-python-0.10.10/testsuite/test_interface.py", line 49 in setUp
    self.mixer = gst.element_factory_make('alsasrc', '')
ElementNotFoundError: alsasrc

----

On Solaris, we support OSS and SunAudio.  It seems bad that the testsuite only works with ALSA.  If I change the alsasrc reference to osssrc, it still doesn't work with these errors:

AttributeError: '__main__.GstOssSrc' object has no attribute 'probe_get_properties'
AttributeError: '__main__.GstOssSrc' object has no attribute 'probe_get_property'
AttributeError: '__main__.GstOssSrc' object has no attribute 'probe_get_values_name'

I see similar errors if I try changing it to sunaudiosrc.

-----

I also notice ALSA is hardcoded into the GStreamer Pipeline tester in examples/pipeline-tester.  Note test "Sound capture via ALSA" and "Reencode Vorbis to mulaw, play via ALSA", and "Streaming Ogg/Theora+Vorbis playback, tee to disk.  Shouldn't these tests check whatever sink & source you have defined on the system and use those?  These tests seem to work okay if I hardcode them to use osssrc and osssink rather than the ALSA ones.

I also see a few problems running pipeline-tester:

The "Software scaling" test complains "Could not create pipeline.  could not link videoscale1 to ximagesink3.  Not sure why this is failing.

The "Reencode Vorbis to mulaw, play via alsa" does not work if you run the /usr/share/gst-python/0.10/examples/pipeline-tester (rather than running the version in the source tree), complaining it can't find the file cooldance.ogg
Considering the file is only 74K (only twice as large as the remuxer.py example), perhaps installing this ogg file to the examples directory would be 
nice.

The "Streaming Ogg/Theora+Vorbis playback, tee to disk" test fails if you run it from a directory where you don't have write permissions, like if you cd to /usr/share/gst-python/0.10/examples, and run pipeline-tester.  Might be nice if the test did a change-directory into the /tmp directory or something to do this test.

The V4L and DV tests only work if you have these plugins installed, which are not present currently on Solaris.  Might be nice to disable these choices if the plugins are not present.

Whenever some tests fail (such as the "Streaming Ogg/Theora+Vorbis playback, tee to disk" failure mentioned above), the Stop button doesn't change to a Play 
button.  This is annoying since it means you have to stop and restart the test 
program to run any further tests.
Comment 1 Brian Cameron 2008-02-22 02:24:05 UTC
I filed the pipeline-tester bugs in a separate bug report, bug #517993.

Just to keep things easy, this bug report can just be about the gst-python 
testsuite failing on Solaris.
Comment 2 Edward Hervey 2010-04-29 14:06:12 UTC
Brian, do we still need this bug opened ?
Comment 3 Brian Cameron 2010-04-29 16:20:44 UTC
I just ran "make check" in the testsuite directory and all the tests pass, so closing this bug.  Thanks for the heads up.
Comment 4 Tim-Philipp Müller 2010-05-11 09:14:47 UTC
Marking as obsolete, since we don't really know when/where/how it got fixed.