On Sat, 2012-04-14 at 11:28 +0200, Thomas Pequet wrote: > Le 13/04/2012 17:16, Patrick Ohly a écrit : > > On Mi, 2012-04-11 at 11:43 +0200, Thomas Pequet wrote: > >> Le 10/04/2012 17:30, Patrick Ohly a écrit : > >>> ----------------------------- > >>> > >>> Finding twins during a slow sync fails for calendar events. Although > >>> client and server have exactly the same data, a duplicate item is > >>> created on the client: > >>> > >>> http://syncev.meego.com/2012-04-10-08-05_testing_memotoo/testing-amd64/23-memotoo/Client_Sync_eds_event_testSlowSyncSemantic.log.html > >>> > >>> Populate server: > >>> http://syncev.meego.com/2012-04-10-08-05_testing_memotoo/testing-amd64/23-memotoo/Client_Sync_eds_event_testSlowSyncSemantic.send.client.A/ > >>> > >>> Slow sync: > >>> http://syncev.meego.com/2012-04-10-08-05_testing_memotoo/testing-amd64/23-memotoo/Client_Sync_eds_event_testSlowSyncSemantic.slow.client.A/ > >> May be it come from the previous ID problem. > >> Can you try again ? > > No, still fails. I reran the test manually, so logs are not public yet. > Ok I think I have corrected this :)
Yes, seems fixed: http://syncev.meego.com/2012-04-13-15-25_all/testing-amd64/nightly.html#memotoo But it's still not all rosy. ------------------------------------- Unexpected update sent back to client: http://syncev.meego.com/2012-04-13-15-25_all/testing-amd64/23-memotoo/Client_Sync_eds_event_testCopy.log.html Could this be related to a change for handling the case where the server resolves a conflict (see earlier discussion around testMerge)? Or perhaps it is simply a timing issue? If it is timing, then the client-side test driver cannot do anything about it, because it happens inside a single sync session. In the testCopy case, client A is sending an item that the server doesn't have (Add). Why is the server sending back an update for it? Send: http://syncev.meego.com/2012-04-13-15-25_all/testing-amd64/23-memotoo/Client_Sync_eds_event_testCopy.send.client.A/syncevolution-log_trm002_003_outgoing.xml Update (same session): http://syncev.meego.com/2012-04-13-15-25_all/testing-amd64/23-memotoo/Client_Sync_eds_event_testCopy.send.client.A/syncevolution-log_trm003_006_incoming.xml testCopy only failed for events, worked for contacts, tasks and notes. Same failure in testAddUpdate for events (Add command) *and* tasks (but at a different part of the test, after the Replace command). I've spot-checked some of other failures, they all seem to be about this unexpected update. ------------------------------------- -- 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
