Hello Thomas! For a while I only ran basic sanity checks. Now I've (finally) adapted the Memotoo test data to "all time stamps are floating" and reran the full set of tests:
http://syncev.meego.com/2012-02-21-13-43_all/testing-amd64/nightly.html#memotoo http://syncev.meego.com/2012-02-23-13-26_testing_memotoo_davical_apple/testing-amd64/nightly.html#memotoo There are several tests which fail because the server sends changes to the client when it shouldn't, because the client already has the latest data. For example: http://syncev.meego.com/2012-02-23-13-26_testing_memotoo_davical_apple/testing-amd64/23-memotoo/Client_Sync_eds_task_testUpdate.log.html Do you have an idea where that might come from? You can navigate to the individual sync logs by following the links in "starting Client_... with sync mode ...". -- 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
