I'm trying to fix this as discussed in IRC, that is respawning the D-Bus test connection (and related mock services) at every test, and having a longer timeout.
However I'm getting a crash when calling startServices(): http://paste.ubuntu.com/20160205/ The crash seems to happen after one Accounts::Manager object has been created, and must be related to D-Bus: if I comment out all "new Accounts::Manager()" from the tests or if I add the Accounts::Manager::DisableNotifications option to the Accounts::Manager constructor (which effectively disables any usage of D-Bus in the library), I don't get any crash when invoking startServices() in later tests. I'm still trying to understand why this happens. Note that libaccounts- qt doesn't use D-Bus itself: it wraps libaccounts-glib, which calls g_bus_get_sync (G_BUS_TYPE_SESSION, NULL, &error_int); This must return the right thing, as the testAccountChanges() test works fine itself -- it just causes any startServices() invoked afterwards to fail. Will continue investigating... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603706 Title: Possible races in tst_daemon tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/online-accounts-api/+bug/1603706/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
