Re: [SyncEvolution] Memotoo: updating event + todo ignored?

On Sa, 2011-03-05 at 11:02 +0000, Thomas Pequet wrote: Here's the problem description with updated links: Some tests related to sending an updated event or task to the server which fail (testUpdate, testAddUpdate). What I see is that client A sends an updated to the server. Then client B syncs in two-way and should be sent that update, but doesn't get it: Overview: http://runtests.syncevolution.org/2011-03-02-21-30/head-evolution-testing... Add item log: http://runtests.syncevolution.org/2011-03-02-21-30/head-evolution-testing... [2011-02-05 11:14:29.750] RECEIVED STATUS 201 for for command 'Add' (outgoing MsgID=2, CmdID=5) Send update log: http://runtests.syncevolution.org/2011-03-02-21-30/head-evolution-testing... [2011-02-05 11:15:08.678] RECEIVED STATUS 200 for for command 'Replace' (outgoing MsgID=2, CmdID=5) ... [2011-02-05 11:15:12.237] Successful end of session -> calling engFinishDataStoreSync() for datastores now Receive update log (without the update): http://runtests.syncevolution.org/2011-03-02-21-30/head-evolution-testing... [2011-02-05 11:15:22.313] ---- System time in UTC : 2011-02-05 11:15:22.313 A different test (testAddUpdate) which adds the item from client A and then updates it from A before sending to B implies that the item doesn't seem to be updated on the server (client B gets the old data) - I haven't verified that in the web interface, though. The time stamps on the client show that the last session with client B starts 10 seconds after the end of the previous session with client A, and roughly 14 seconds after the item was updated on the server. -- 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.