Hi Patrick !
It is strange because normally it works. Normally there is no cache data
so the event is sent to client B
Can you try again, and wait 1 minute before sync the client B ?
--
See you soon on Memotoo !
Thomas Pequet - Webmaster Memotoo
https://www.memotoo.com/profile/thomas.memotoo
Le 06/02/2011 11:22, Patrick Ohly a écrit :
Hello Thomas!
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-02-05-04-52/head-evolution-testing/13-memotoo/Client_Sync_ical20_testUpdate.log
Add item log:
http://runtests.syncevolution.org/2011-02-05-04-52/head-evolution-testing/13-memotoo/Client_Sync_ical20_testUpdate.send.client.A/
Send update log:
http://runtests.syncevolution.org/2011-02-05-04-52/head-evolution-testing/13-memotoo/Client_Sync_ical20_testUpdate.update.client.A/
Receive update log (without the update):
http://runtests.syncevolution.org/2011-02-05-04-52/head-evolution-testing/13-memotoo/Client_Sync_ical20_testUpdate.update.client.B/
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.
Any idea?
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
