On Di, 2012-07-31 at 10:35 +0200, Patrick Ohly wrote:
On Di, 2012-07-31 at 10:18 +0200, Vladimir Elisseev wrote:
> See debug log: http://pastebin.com/PmUaCrwx
> Personally, based on the debug info, I can't understand what's going on.
The relevant part is here:
[DEBUG syncevo-dbus-server 00:30:00] auto sync: reschedule, funambol interval timer
[DEBUG syncevo-dbus-server 00:30:00] auto sync: funambol:
[DEBUG syncevo-dbus-server 00:30:00] auto sync: funambol: presence delay of transport for
expires in -1500s
Somehow the check for "have we been online long enough" fails. Probably
another side effect of not really having a running network manager of
any kind - I'll check.
Actually, autoSyncDelay > 0 (the default) was broken in general. Thanks
a lot for trying this out! It'll be fixed in the next release.
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Thu Aug 2 11:16:02 2012 +0200
D-Bus server: fix support for autoSyncDelay > 0
Auto syncing was not getting triggered when using an autoSyncDelay > 0;
by default it is 5 minutes. Thanks to Vladimir Elisseev for reporting
The root cause was a "greater than" instead of a "less than"
comparison. This was not found by the tests because they set
autoSyncDelay to zero to speed up testing.
Changing one test (TestSessionAPIsDummy.testAutoSyncNetworkFailure) so
that it uses non-zero autoSyncDelay triggered the problem. Also added
a variation of that test that simulates the "no Connman and no
NetworkManager" setup used by Vladimir.
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.