http://bugzilla.moblin.org/show_bug.cgi?id=3427 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|poor usability with network |poor usability with network |interruption |interruption: resend | |messages --- Comment #22 from pohly <patrick.ohly(a)intel.com&gt; 2009-09-15 07:29:40 --- The workaround for the endless Alert 222 loop has been merged by Synthesis and is in our "master" branch. Congwu, can you enable the message resending again in the nightly testing? How much does it increase the duration of the nightly test run? Last week on the train I noticed one problem with the implementation: when the network is down completely, starting a sync via the command line reported that the initial message was sent three times. It did that quickly without any apparent delay between the attempts. However, I cannot reproduce that anymore. When trying to reproduce it now I get a different kind of failure: [INFO] SoupTransport Failure: http://my.funambol.com/sync/ via libsoup: Cannot resolve hostname [ERROR] proceeding with session failed [INFO] vcard21: normal sync done unsuccessfully This is with the latest Synthesis code and thus the slightly different Synthesis engine state machine. "proceeding with session failed" comes from a Synthesis error code: src/core/SynthesisEngine.cpp: throw BadSynthesisResult("proceeding with session failed", static_cast<sysync::TSyErrorEnum>(err)); It seems that our code must be adapted to the upstream Synthesis engine. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.