https://bugs.meego.com/show_bug.cgi?id=21541

           Summary: D-Bus server:
    Classification: MeeGo Projects
           Product: SyncEvolution
          Platform: ---
           Version: unspecified
          Platform: Common
      Architecture: ---
            Status: NEW
          Severity: normal
          Priority: Undecided
         Component: SyncEvolution
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]
                CC: [email protected],
                    [email protected]
   Estimated Hours: 0.0


>From nightly testing, shortly after 1.1.99.5:

TestDBusServerPresence.testPresenceSignal - check Server.Presence signal ...
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in
maybe_handle_message
    self._handler(*args, **kwargs)
  File "/work/runtests/head/syncevolution/test/test-dbus.py", line 973, in
cb_bt_presence
    "obex-bt://temp-bluetooth-peer-changed-from-http")
  File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual
    (msg or '%r != %r' % (first, second))
AssertionError: dbus.UTF8String('http://http-only-1') !=
'obex-bt://temp-bluetooth-peer-changed-from-http'
ok

The test needs to be fixed, it shouldn't test assertions inside the callback
because the D-Bus layer swallows these exceptions. Found after adding "-u" to
the python invocation (disabled buffering of stdout).

--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords: 
Status: NEW
Who: [email protected]
Assigned To: [email protected]
Target Build: ---
Flags: 
Changed: 
--------

https://bugs.meego.com/show_bug.cgi?id=21541


-- 
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to