GNOME Bugzilla – Bug 705103
evolution-data-server-3.8.4: test-client-self failed
Last modified: 2018-10-17 15:26:50 UTC
We get: PASS: test-client-add-and-get-async /EBookClient/Self/Get: Activating service name='org.gnome.evolution.dataserver.Sources1' Successfully activated service 'org.gnome.evolution.dataserver.Sources1' Activating service name='org.gnome.evolution.dataserver.AddressBook5' Successfully activated service 'org.gnome.evolution.dataserver.AddressBook5' OK /EBookClient/Self/Set: (/var/tmp/portage/gnome-extra/evolution-data-server-3.8.4/work/evolution-data-server-3.8.4/tests/libebook/client/.libs/test-client-self:17597): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed cleaning up pid 17613 /bin/sh: línea 5: 17597 `trap' para punto de parada/seguimiento (`core' generado) ${dir}$tst FAIL: test-client-self /EBookClient/AddContact/PreserveUid: Activating service name='org.gnome.evolution.dataserver.Sources1' Successfully activated service 'org.gnome.evolution.dataserver.Sources1' Activating service name='org.gnome.evolution.dataserver.AddressBook5' Successfully activated service 'org.gnome.evolution.dataserver.AddressBook5' OK
Test works fine here. Sometimes these D-Bus tests have the occasional hiccup.
I have just hit a different one: /ECalClient/CreateObject/Async: (/var/tmp/portage/gnome-extra/evolution-data-server-3.8.4-r1/work/evolution-data-server-3.8.4/tests/libecal/client/.libs/test-client-create-object:960 2): e-test-server-utils-ERROR **: Unable to create the test calendar: Unable to connect to 'Unnamed': No such source for UID 'test-calendar-1' cleaning up pid 9618 /bin/sh: línea 5: 9602 `trap' para punto de parada/seguimiento (`core' generado) ${dir}$tst FAIL: test-client-create-object /ECalClient/RemoveObject/Sync: Activating service name='org.gnome.evolution.dataserver.Sources1' Successfully activated service 'org.gnome.evolution.dataserver.Sources1' Activating service name='org.gnome.evolution.dataserver.Calendar4' Successfully activated service 'org.gnome.evolution.dataserver.Calendar4' OK /ECalClient/RemoveObject/Async: OK /ECalClient/RemoveObject/EmptyUid: OK Is there a way to try to not get that random failures so often? If they are known to fail, why don't disable them? (or have a configure flag for only run them when really really wanted?) Thanks
Does this problem still happen in recent versions (3.18 or 3.20) or can this be closed as obsolete nowadays?
I'm closing this as obsolete.