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 628085 - gdbus-connection: /gdbus/connection/filter test fails
gdbus-connection: /gdbus/connection/filter test fails
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gdbus
2.25.x
Other Linux
: Normal normal
: ---
Assigned To: David Zeuthen (not reading bugmail)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-08-27 02:34 UTC by Priit Laes (IRC: plaes)
Modified: 2018-05-24 12:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
debug report documenting same error in glib-2.26.0 build (32.22 KB, text/plain)
2010-10-05 08:21 UTC, markus.isler 		Details

Description Priit Laes (IRC: plaes) 2010-08-27 02:34:04 UTC 
When testing glib-2.25.14 tarball (with sys-apps/dbus-1.2.24-r1, Gentoo), I ran into following issue:

[snip]
TEST: gdbus-connection... (pid=5336)
  /gdbus/connection/basic:                                             OK
  /gdbus/connection/life-cycle:                                        OK
  /gdbus/connection/send:                                              OK
  /gdbus/connection/signals:                                           OK
  /gdbus/connection/filter:                                            FAIL
GTester: last random seed: R02S0852425128c9ec0c3f9d3f32be129611
[/snip]
Comment 1 Felipe Besoaín Pino 2010-08-27 04:30:26 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 628084 ***
Comment 2 Priit Laes (IRC: plaes) 2010-08-27 06:03:59 UTC 
(In reply to comment #1)
> Thanks for the bug report. This particular bug has already been reported into
> our bug tracking system, but please feel free to report any further bugs you
> find.
> 
> *** This bug has been marked as a duplicate of bug 628084 ***

Sorry, missed changing the bug the title after cloning the bug ;)
Comment 3 David Zeuthen (not reading bugmail) 2010-08-27 14:27:35 UTC 
Interesting. Please attach the output when running

 $ G_DBUS_DEBUG=call,signal,incoming,emission,transport ./gdbus-connection

from the gio/tests directory. Thanks.
Comment 4 Priit Laes (IRC: plaes) 2010-08-28 15:57:59 UTC 
(In reply to comment #3)
> Interesting. Please attach the output when running
> 
>  $ G_DBUS_DEBUG=call,signal,incoming,emission,transport ./gdbus-connection
> 
> from the gio/tests directory. Thanks.

This smells like a heisenbug as I cannot reproduce it anymore :S
Comment 5 Priit Laes (IRC: plaes) 2010-08-28 16:33:56 UTC 
Apparently gdbus tests do not properly clean up after they exit and leave g-dbus-tests-pid-PIDNR files behind. It might be that when test gets assigned PID number which has existing socket file in tmp is causing the failure.
Comment 6 markus.isler 2010-10-05 08:21:20 UTC 
Created attachment 171743 [details]
debug report documenting same error in glib-2.26.0 build
Comment 7 David Zeuthen (not reading bugmail) 2010-10-05 13:59:50 UTC 
(In reply to comment #6)
> Created an attachment (id=171743) [details]
> debug report documenting same error in glib-2.26.0 build

Why is this the same? This is caused simply by not having the required python packages installed. Just install the packages and the tests should pass.
Comment 8 Murray Cumming 2013-01-25 08:25:34 UTC 
(In reply to comment #7)
> Just install the packages and the tests should pass.

So maybe this is a duplicate of bug #684495 about there being no check for Python in the configure step.
Comment 9 Priit Laes (IRC: plaes) 2013-01-25 08:48:23 UTC 
(In reply to comment #8)
> (In reply to comment #7)
> > Just install the packages and the tests should pass.
> 
> So maybe this is a duplicate of bug #684495 about there being no check for
> Python in the configure step.

Nope, real issue seems to be issue I gave in comment #5
Comment 10 GNOME Infrastructure Team 2018-05-24 12:44:28 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/340.