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 724073 - gstbus test fails with GLib 2.39.1
gstbus test fails with GLib 2.39.1
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.0.10
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-02-10 21:57 UTC by Ludovic Courtès
Modified: 2014-05-26 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
stderr + stdout of 'gst/gstbus' (1.13 MB, application/octet-stream)
2014-02-10 21:57 UTC, Ludovic Courtès 		Details

Description Ludovic Courtès 2014-02-10 21:57:41 UTC 
Created attachment 268739 [details]
stderr + stdout of 'gst/gstbus'

In the GNU Guix repo, the upgrade of GLib from 2.38.0 to 2.39.1 is apparently responsible for a new test failure, 'tests/check/gst/gstbus':

  $ make check TESTS=gst/gstbus
  [...]
  make[1]: Entering directory '/tmp/nix-build-gstreamer-1.0.10.drv-0/gstreamer-  1.0.10/tests/check'
  Running suite(s): GstBus


  Unexpected critical/warning: Source ID 1 was not found when attempting to remove it
  90%: Checks: 10, Failures: 1, Errors: 0
  gstcheck.c:72:F:stresstest:test_watch_with_custom_context:0: Unexpected   critical/warning: Source ID 1 was not found when attempting to remove it
  FAIL: gst/gstbus

Attached is the output of the same test with 'GST_DEBUG=*:9 G_DEBUG=fatal_warnings'.

Thanks,
Ludo'.
Comment 1 Sebastian Dröge (slomo) 2014-05-26 13:06:41 UTC 
This seems to work just fine here with latest 1.2 and git master and glib 2.40.0. Is it still a problem for you?
Comment 2 Ludovic Courtès 2014-05-26 14:53:38 UTC 
No, everything is now fine with 1.0.10, GLib 2.19.1, and libc 2.19.  In the meantime libc was upgraded to from 2.18 to 2.19, but it's unclear what caused the problem to vanish...

Thanks.
Comment 3 Ludovic Courtès 2014-05-26 14:54:05 UTC 
I meant GLib 2.39.1.