Hello Thomas! When testing SyncEvolution 1.1.99.7, Memotoo worked fine:
http://syncev.meego.com/2011-09-15-10-33_all_syncevo=syncevolution-1-2-branch/head-testing-amd64/nightly.html#memotoo The failures in testAddBothSides are understood and acceptable (add<->add conflict where the test assumes that the server matches based on UID, which Memotoo doesn't to), same for testExtensions (not all vCard extensions supported). But now I see a lot of the same tests failing. Admittedly I also changed some parts of SyncEvolution, but I can't imagine why that should have such an effect: http://syncev.meego.com/2011-10-07-08-56_testing_apple_davical_oracle_egroupware-dav_memotoo_mobical_syncevo=calconnect_synthesis=bmc22783/head-testing-amd64/nightly.html#memotoo For example, STATUS:NEEDS-ACTION is getting lost on the server. I checked that it is sent and doesn't come back: http://syncev.meego.com/2011-10-07-08-56_testing_apple_davical_oracle_egroupware-dav_memotoo_mobical_syncevo=calconnect_synthesis=bmc22783/head-testing-amd64/20-memotoo/Client_Sync_eds_task_testCopy.send.client.A/syncevolution-log.html http://syncev.meego.com/2011-10-07-08-56_testing_apple_davical_oracle_egroupware-dav_memotoo_mobical_syncevo=calconnect_synthesis=bmc22783/head-testing-amd64/20-memotoo/Client_Sync_eds_task_testCopy.recv.client.B/syncevolution-log.html Event tests fails because I added a recurring all-day event with EXDATEs, which is converted by Memotoo (known issue) to a fixed-time event. I'll remove that test case for Memotoo. -- 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
