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. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
