Le 30/03/2012 09:02, Patrick Ohly a écrit :
On Tue, 2012-03-27 at 18:10 +0200, Thomas Pequet wrote:
But perhaps you see something in the server-side logs already?
Sorry there was a easy bug to correct and now it is better :)
Can you try again ?
I ran the full set of tests:
http://syncev.meego.com/latest/testing-amd64/nightly.html#memotoo
Many thanks Patrick :)

The testManyItems for events failed with something that looks like an
internal error in EDS and/or SyncEvolution. It is unclear why the
following item was asked for in the first place. I'll investigate:

[ERROR 00:00:53] error code from SyncEvolution object not found (remote, status 
404): eds_event: retrieving item: 008-1234567890!@#$%^-rid
http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_testManyItems.log.html
I have corrected the MoreData bug, so may be it will be better for testManyItems. I think the problem code from Memotoo with the new version. Give me the XML and I think I will see the problem


In a case where<MoreData>  was necessary the server rejected the second
chunk of the<Add>  with a 500 error:
http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_eds_task_eds_memo_eds_contact_testTwinning.twinning.client.A/syncevolution-log.html#SO_3_3
http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_eds_task_eds_memo_eds_contact_testTwinning.twinning.client.A/syncevolution-log.html#IO_3_3

First part:
http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_eds_task_eds_memo_eds_contact_testTwinning.twinning.client.A/syncevolution-log_trm002_003_outgoing.xml
Second part:
http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_eds_task_eds_memo_eds_contact_testTwinning.twinning.client.A/syncevolution-log_trm003_005_outgoing.xml
500 error:
http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_eds_task_eds_memo_eds_contact_testTwinning.twinning.client.A/syncevolution-log_trm003_006_incoming.xml

Does Memotoo support<MoreData>?
Yes but there was a bug with new version.
Now I have corrected this problem.
Can you start a new test ?

That issue probably also affects some more (no pun intented) of the
tests involving large items (testMaxMsg, testLargeObject).

Memos don't seem to be affected, but I suspect that this is merely
because splitting a plain text into two halves doesn't result in
unparsable items.

_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to