[SyncEvolution] D-Bus Testing + TestSessionAPIsReal + StatusChanged "done" multiple times

Hello! There's currently a problem with the D-Bus API testing when the TestSessionAPIsReal test suite is run so that both of its tests run real syncs. I've looked into this in more detail and found that it is because the first test sets up a D-Bus signal handle for StatusChanged which calls loop.quit() when status == "done". Then our server fires that state *multiple* times for the first sync. The first signal finishes the first test. The second signal the second, although that sync isn't done yet. Debugging this was hard because the reasons why loop.quit() were called were also recorded per test, so they weren't visible in the second test. I'm changing that. I'm also still looking at why the "done" signal is sent more than once. I think that shouldn't happen. Suggestions welcome, in case that I don't finish this today (not unlikely, it's late and I have a choir rehearsal for a performance on Sunday...). -- 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.