Hello Chris! One comment on your commit in the test-dbus branch:
----------------------------------- commit da74d2aa1b671c0794cd88a854e137ae93ee102a Author: Chris Kühl <[email protected]> Date: Tue Jun 28 14:48:56 2011 +0200 test-dbus: Remove check for only one report. Whenever there is an existing sync report in the cache directory, the testSync test fails. This fixes that, albeit probably naively. diff --git a/test/test-dbus.py b/test/test-dbus.py index b6d99c4..083e8b5 100755 --- a/test/test-dbus.py +++ b/test/test-dbus.py @@ -636,7 +636,7 @@ class DBusUtil(Timeout): # now check that report is sane reports = self.session.GetReports(0, 100, utf8_strings=True) - self.assertEqual(len(reports), 1) + #self.assertEqual(len(reports), 1) if expectedResult: self.assertEqual(int(reports[0]["status"]), expectedResult) ----------------------------------- "the cache" directory should be ./test-dbus/cache/syncevolution, which is getting cleared before running each test. See the xdg_root part of test-dbus.py. Which test has the problem with too many reports? Does it use its own XDG root? -- 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
