Re: [SyncEvolution] New version of Memotoo server

On Sat, 2012-04-14 at 11:28 +0200, Thomas Pequet wrote: Yes, seems fixed: http://syncev.meego.com/2012-04-13-15-25_all/testing-amd64/nightly.html#m... 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/Cli... 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/Cli... Update (same session): http://syncev.meego.com/2012-04-13-15-25_all/testing-amd64/23-memotoo/Cli... 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.