On Mon, 2011-11-21 at 16:50 +0100, Thomas Pequet wrote: > > Le 21/11/2011 16:45, Patrick Ohly a écrit : > > On Mon, 2011-11-21 at 16:08 +0100, Thomas Pequet wrote: > >> I think I have solved the problem. > >> Can you run again the test ? > > With which delay? 5 seconds used to work, but more recently only 10 > > seconds avoided problems with change tracking. > Try with 5 seconds I think it will be good.
With 5 seconds I ran into timing related problems again: http://syncev.meego.com/2011-11-21-20-23_syncevo=syncevolution-1-2-branch_all/testing-amd64/nightly.html#memotoo Test name: Client::Sync::eds_event::testManyDeletes equality assertion failed - Expected: 0 - Actual : 1 - eds_event: clientUpdated == source.getItemStat(SyncSourceReport::ITEM_LOCAL, SyncSourceReport::ITEM_UPDATED, SyncSourceReport::ITEM_TOTAL) Rerunning this test succeeds. A full test run against Memotoo already takes over 3 hours. I don't know how much of that is spent waiting - probably not that much, so I'll just increase the delay. The twinning issue seems to be resolved. -- 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
