Comment 1 for bug 1603706

I definitely see how these failures can happen: the tests set the OnlineAccounts.Manager service's auto-termination timeout to 2 seconds, which is generally appropriate. However, the testAccountChanges() test is not even trying to keep the service alive, because it's modifying the accounts DB via libaccounts; so, on a slower testing machine, indeed the service could auto-terminate itself during the lifetime of the test.

The error in vivid shows exactly this; in the yakkety case, the auto-termination happens a bit later, allowing the testAccountChanges() test to succeed, but then by the time the next test (testLifetime()) sets up its watch, the OnlineAccounts.Manager service has already quit, causing the other test to fail.