[Bug 46971] New: [next] regression in tests/dbus/self-presence

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Mar 5 13:23:07 CET 2012


https://bugs.freedesktop.org/show_bug.cgi?id=46971

             Bug #: 46971
           Summary: [next] regression in tests/dbus/self-presence
    Classification: Unclassified
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: ASSIGNED
          Keywords: patch
          Severity: normal
          Priority: medium
         Component: tp-glib
        AssignedTo: simon.mcvittie at collabora.co.uk
        ReportedBy: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org
                CC: jonny.lamb at collabora.co.uk


Created attachment 58020
  --> https://bugs.freedesktop.org/attachment.cgi?id=58020
tests: wait for CONNECTED feature where we used to

Commit 2be1aca4e3 caused an intermittent regression in
tests/dbus/self-presence.c. The example Connection we use only makes
its statuses available when the connection has connected, simulating a
CM like Gabble where available statuses are discovered during connection.

Previously, we used tp_connection_run_until_ready() which effectively
waits for the CONNECTED feature; in that commit, I switched to using
tp_tests_proxy_run_until_prepared() which does not, unless you ask for
it. As a result, there was a race between Get(..., "Statuses") and the
connecting process, leading to intermittent (1/10?) test failures.

This commit updates all tests touched by 2be1aca4e3, except for
invalidated-while-invoking-signals.c which doesn't actually need to
reach the CONNECTED status.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.



More information about the telepathy-bugs mailing list