On Fri, 2012-03-30 at 15:16 +0200, Thomas Pequet wrote: > Le 30/03/2012 11:31, Patrick Ohly a écrit : > > On Fri, 2012-03-30 at 09:32 +0200, Thomas Pequet wrote: > >> Le 30/03/2012 09:02, Patrick Ohly a écrit : > >>> 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, > > Confirmed, that seems to work now (manual tested, still need to run the > > full suite again). > > > >> 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 > > It's indeed on the server side. The server seems to truncate the local > > ID at the& sign. > > > > <Add> command sent to server: > > http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_testManyItems.send.client.A/syncevolution-log_trm002_003_outgoing.xml > > > > <Status> received back: > > http://syncev.meego.com/latest/testing-amd64/23-memotoo/Client_Sync_eds_event_testManyItems.send.client.A/syncevolution-log_trm002_004_incoming.xml > > > > I know, I am a nasty bugger for sending such tricky characters in the > > local ID, but these are the corner cases which have to be tested>:-> > You have right to want to test all case ! :) > Theses links do not work ... Can you send me the good link to see the XML ?
Replace "/latest/" with "/2012-03-29-17-01_testing_memotoo/" and you'll find the files. -- 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
