On Tue, 2011-07-05 at 09:40 +0200, Chris Kühl wrote: > With these changes, I'm down to only one failure
The one about TestDBusSession.testSecondSession, right? I'm looking at it now. As I suspected, the Connman class is to blame. The mock class remains active and then messes with the mainloop, which confuses the other test. > Unfortunately, the "same results" > means that it also has the defaultPeer issue which I'm trying to find > a fix for. See my other mail about how defaultPeer should be stored (gdb back traces, etc.). Note that you can set debugger = "gdb" at the top of test-dbus.py to invoke an interactive debug session on syncevo-dbus-server while running a single test. -- 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
