On Mi, 2011-11-16 at 11:58 +0100, Patrick Ohly wrote: > On Mi, 2011-11-16 at 11:10 +0100, Chris Kühl wrote: > > On Mon, Nov 14, 2011 at 4:49 PM, Chris Kühl <[email protected]> wrote: > > > On Mon, Nov 14, 2011 at 2:31 PM, Patrick Ohly <[email protected]> > > > wrote: > > > Ok. We should be close to requesting a merge. Only 2 failures to fix > > > before we've reached parity on our machines. > > > > > > > After fixing those remaining issues, we ran the server under valgrind > > and fixed up a few memory leaks we found. I've now created a > > for-master/gio-gdbus branch, squashed the commits and pushed. > > I've started a test run.
There seems to be a regression in the D-Bus testing. On Ubuntu Lucid, startup of the syncevo-dbus-server without GIO GDBus fails: http://syncev.meego.com/2011-11-16-10-54_dist/lucid-amd64/6-dbus/output.txt 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 The nightly.html doesn't properly report the individual D-Bus errors, only the overall failure is correctly reported - I will investigate that. For comparison, this used to work in the previous test run: http://syncev.meego.com/2011-11-12-12-51_all/lucid-amd64/nightly.html Linking on Debian Testing fails because some library symbol is used without directly linking against that library (the binutils on that platform are more demanding and check for this): http://syncev.meego.com/2011-11-16-10-54_dist/gcc-4.6-amd64/3-compile/output.txt It should be fairly easy for me to fix these issues, while it is harder for you unless you have access to the right platforms or know what the issue is. Just let me know if you want me to lend a hand. -- 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
