On Tue, Nov 29, 2011 at 12:12 PM, Patrick Ohly <[email protected]> wrote: > On Mo, 2011-11-28 at 12:24 +0100, Chris Kühl wrote: >> On Wed, Nov 16, 2011 at 2:52 PM, Patrick Ohly <[email protected]> wrote: >> > 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 >> > >> >> So, I finally got the issue in Debian Stable and Ubuntu LTS fixed. >> Turned out to be that I'd inadvertently set the server's main >> connection to shared instead of private. I'm not sure why this was >> only causing issues on these distros. That initially sent me searching >> for the issue in all the wrong places. > > lucid-amd64 without GIO GDBus passed the tests now. I had to take the > for-master/gio-gdbus branch temporarily out of testing because the > autoconf changes conflicted with another branch, but now it is back and > was tested. > > However, it segfaults during startup on Debian Testing with GIO GDBus > enabled: > http://syncev.meego.com/latest/testing-amd64-gio/6-dbus/output.txt >
Link is broken. But I've not had that issue with Debian Testing. Hmm? I've got a clean install with only the necessary packages added for building and running syncevolution. > I'm going to have a look and then merge. As long as it doesn't cause > regressions and isn't enabled by default, I don't mind fixing problems > in new features on the master branch. Hmm, wait, GIO GDBus is used by > default if enabled. Let's see... > Feel free to change the default to use the bluez code if you feel more comfortable with that. But I'd assume we will eventually want this to be the default. >> Along the way I was also able to fix the --enable-notify flag which >> was broken. You can now actually disable notifications. >> >> This will all be in for-master/gio-gdbus within the next hour or so. >> >> > 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 > > This was the temporary plan44.ch server issue. > Yes, I saw that. Cheers, Chris _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
