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 627188 - gdbus-non-socket test occasionally fails
gdbus-non-socket test occasionally fails
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gdbus
unspecified
Other Linux
: Normal normal
: ---
Assigned To: David Zeuthen (not reading bugmail)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-08-17 16:47 UTC by Christian Persch
Modified: 2010-08-18 17:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Persch 2010-08-17 16:47:55 UTC
When the system is under heavy load, the gdbus-non-socket test fails. I can reproduce this with "while ./gdbus-non-socket; do sleep 1; done" where it will eventually either produce either this error:

ERROR:gdbus-non-socket.c:305:test_non_socket: assertion failed (error == NULL): GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gtk.GDBus.Pokee' on object at path /pokee (g-dbus-error-quark, 19)
Abgebrochen (Speicherabzug geschrieben)
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

or this error:

ERROR:gdbus-non-socket.c:305:test_non_socket: assertion failed (error == NULL): Timeout was reached (g-io-error-quark, 24)
Abgebrochen (Speicherabzug geschrieben)

The random seed appears not to be involved; re-running the test with the seed of the failed run doesn't repro the failure; only running the test under load or in a loop does.

This is glib master from today, on fedora 13.
Comment 1 David Zeuthen (not reading bugmail) 2010-08-17 17:25:17 UTC
I can reproduce this, will investigate + fix later (unless you beat me to it!)
Comment 2 David Zeuthen (not reading bugmail) 2010-08-18 17:10:16 UTC
OK, this was actually a wrong assumption in the test case (see commit for details). With this fix

 http://git.gnome.org/browse/glib/commit/?id=7d6a6ca57b5a5dc1ad55a785dfd79fa98d7e4093

I can no longer reproduce this problem. Closing. Thanks.