We did spend some time on the anchors but have as yet been unable to work out how it's happening. It's still an open issue.
D. -----Original Message----- From: Patrick Ohly [mailto:[email protected]] Sent: Tuesday, July 28, 2009 9:50 AM To: SyncEvolution Cc: Bower, David, VF-Group Subject: Re: SyncML Tests 2009-07-27: head-evolution-testing Hello! Analysis of latest nightly run below. On Tue, 2009-07-28 at 04:47 +0100, Ohly, Patrick wrote: > http://runtests.syncevolution.org/2009-07-27-22-00/head-evolution-testin g > > libsynthesis successful > syncevolution successful > compile successful > dist skipped: disabled in configuration > evolution successful This worked on all of the other platforms, too. The problem with not finding the default memo in earlier runs was a local install problem: I'm pretty sure I had started Evolution once in each platform and opened addressbook, calendar, tasks, memos, but despite that, the system memo lists didn't exist on all platforms. It seems it is necessary to create an entry in Evolution before it creates the database. > scheduleworld: failed Fails because of the new testSlowSyncSemantic test (#4703). I have added it to the list of know failures and will document it in a test/README.scheduleworld if it doesn't get resolved. > memotoo skipped: disabled in configuration > egroupware skipped: disabled in configuration > synthesis: failed Only one failure: ClientTest.cpp:3851:Assertion Test name: Client::Sync::text_vcard21::Suspend::testUserSuspendClientRemove equality assertion failed - Expected: 0 - Actual : 500 This was because of a timeout, according to the log at the start of the sync session. Because the "timestampall" option is not set in the Synthesis log, it is hard to tell how long that session ran. I have enabled that option now. There's also not enough debug information to identify where it got stuck - communication with EDS perhaps? > funambol: One failure: ClientTest.cpp:3851:Assertion Test name: Client::Sync::itodo20::testCopy equality assertion failed - Expected: 0 - Actual : 20043 [ERROR] http://my.funambol.com/sync via libsoup: Bad Gateway Message resending might have avoided this failure... > zyb: failed Still no word from ZYB. David, is anyone looking at the anchor problem? http://bugzilla.moblin.org/show_bug.cgi?id=2424#c28 > google successful Yeah! Congwu's script for cleaning the server data works. -- 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
