Hello! I've tagged this as 20090730 snapshot and consider it a release candidate for 0.9.
On Fri, 2009-07-31 at 04:48 +0100, Ohly, Patrick wrote: > http://runtests.syncevolution.org/2009-07-30-22-00/head-evolution-testing > > libsynthesis successful > syncevolution successful > compile successful > dist skipped: disabled in configuration > evolution successful No surprises on the other platforms, they all compiled fine. > scheduleworld: failed Mark fixed some issues (twinning for text::testManyItems). He also identified the root cause of the sync failures after a slow sync (the server expected the client's last anchor to be non-empty during a slow sync) which was resolved both in the server (no longer makes that assumption) and the Synthesis library (sends a dummy string). However, twinning of notes still fails in one case: text::testSlowSyncSemantic. Item send during regular sync: http://runtests.syncevolution.org/2009-07-30-22-00/head-evolution-testing/6-scheduleworld/Client_Sync_text_testSlowSyncSemantic.send.client.A/sysynclib_linux.html Item send again during slow sync and comes back as duplicate: http://runtests.syncevolution.org/2009-07-30-22-00/head-evolution-testing/6-scheduleworld/Client_Sync_text_testSlowSyncSemantic.slow.client.A/sysynclib_linux.html This test passes with all other servers. > memotoo skipped: disabled in configuration > egroupware skipped: disabled in configuration > synthesis: failed Two failures: ClientTest.cpp:3887:Assertion Test name: Client::Sync::text_vcard21::Retry::testInterruptResumeServerRemove equality assertion failed - Expected: 0 - Actual : 20043 ClientTest.cpp:3887:Assertion Test name: Client::Sync::text_vcard21::Retry::testInterruptResumeServerUpdate equality assertion failed - Expected: 0 - Actual : 20043 [ERROR] http://www.synthesis.ch/sync2 via libsoup: Connection terminated unexpectedly > funambol successful > zyb: failed The known anchor problem. > google successful -- 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
