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 483692 - Make test fails for GstObject on F7-i386
Make test fails for GstObject on F7-i386
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.14
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-05 12:03 UTC by TTA
Modified: 2009-04-16 19:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description TTA 2007-10-05 12:03:19 UTC
Platform: x86 
OS: Fedora 7-i386
Source: gstreamer-0.10.14 
GCC: gcc (GCC) 4.1.2 20070502 (Red Hat 4.1.2-12)

When trying to set up gstreamer 0.10.14 on the f7-i386 machine , 
configured using: ./configure
test using:       make check   

The result is:
==========================================================================
1 of 51 tests failed
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer
==========================================================================

The failing test is:
Running suite(s): GstObject
87%: Checks: 8, Failures: 1, Errors: 0
gst/gstobject.c:194:F:general:test_fake_object_name_threaded_wrong: name did not get changed
FAIL: gst/gstobject

This is reproducible. I have not tried it on other platforms.
Comment 1 Sebastian Dröge (slomo) 2007-10-05 12:12:05 UTC
I can confirm this, just changing the sleep to something else fixes it for me. Not sure if this makes sense in general... especially for slow machines.

--- gst/gstobject.c     7 Jul 2006 17:16:26 -0000       1.10
+++ gst/gstobject.c     5 Oct 2007 12:10:53 -0000
@@ -138,7 +138,7 @@ GST_END_TEST
   THREAD_START ();
 
   /* give main thread a head start */
-  g_usleep (100000);
+  g_usleep (1000);
 
   /* write our name repeatedly */
   g_message ("THREAD %s: starting loop\n", thread_id);
Comment 2 Tim-Philipp Müller 2009-04-16 19:16:23 UTC
I vaguely remember us fixing this (or the issue disappearing), but can't say I remember any particular fix/commit.

Closing as OBSOLETE for now - if someone can reproduce this with the latest core, please re-open.