On Thu, Nov 17, 2011 at 6:14 PM, Chris Kühl <[email protected]> wrote:
> 2011/11/17 Patrick Ohly <[email protected]>:
>> On Mi, 2011-11-16 at 15:40 +0100, Chris Kühl wrote:
>>> > The same binary runs on Debian Testing, albeit with regressions in
>>> > TestSessionAPIsReal.testSync and
>>> > TestSessionAPIsReal.testSyncSecondSession :
>>> >
>>> http://syncev.meego.com/2011-11-16-10-54_dist/prebuilt-amd64/6-dbus/output.txt
>>> >
>>>
>>> These were failing for me using master on my fedora 15 system so
>>> haven't been properly debugged in gio-gdbus.
>>
>> It turned that the 101 status in these failures is a remote error sent
>> by the plan44.ch SyncML server, which is the server that these real
>> syncs are meant to be done with. I've switched to Memotoo as peer for
>> the D-Bus tests for now.
>>
>> Lukas, any idea about the reason for the 101 error? I don't see any log
>> created for this session on the server. The error occurs right at the
>> start, as the status returned for the initial SyncHdr.
>>
>> --
>
> Ok, thanks for the update and glad to see that's working. I'm still
> trying to work out what's going on with Ubuntu Lucid. I'm getting the
> same result with Debian Stable as well, though. ...back to bug fixing.
>

I've pushed a commit[1] to the gio-gdbus branch that gets the server
starting up fine. Seems to have been a compiler bug. However, I'm
currently getting the following error when running each test.

ERROR:dbus.proxies:Introspect error on
:1.140:/org/syncevolution/Server: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

Tracking this down now.

Cheers,
Chris

[1] 
https://meego.gitorious.org/meego-middleware/syncevolution/commit/e2d5009ff282e67fde5fba4c74e38c92a5fc7af0/diffs/5baf3ad4c78efe23807aca4cd1550080600da18c
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to