On Wed, Mar 14, 2012 at 11:28 AM, Patrick Ohly <[email protected]> wrote: > On Thu, 2012-03-08 at 17:18 +0100, Chris Kühl wrote: >> It's been rebased and we've squashed the changes into about a dozen >> commits. The tests seem to give us the same results as before the >> rebase. > > And those are? In other words, which tests are known to fail, and why? >
I've pushed a branch called css-without-known-test-failures[1] whose most recent commit comments out all the tests in test/test-dbus.py that fail. However, there as a bug I introduced during the last rebase. The fix for that can be found here[2]. All but one of the failures is due to the incomplete AutoSync and Connection functionality. The restart test has never worked for us on any branch. Cheers, Chris [1] https://meego.gitorious.org/meego-middleware/syncevolution/commit/d88052510b77c8236ced646e77ee0d9303bda126 [2] https://meego.gitorious.org/~krnowak/meego-middleware/krnowaks-syncevolution/commit/13896a1df0dfc815037e0749638f03decee507ac _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
