@Charles, [1] Clock and Calendar app *do not* run their AP tests in isolated EDS sandboxes and that is the main issue. We already have a bug report in the clock app requesting for mocking the EDS collection to avoid interacting with the user's alarms and events, let alone the events of another app. But unfortunately I do not have the expertise to add the mocking server for EDS. I will see if I can get the QA team to implement that for the clock and calendar app.
[2] Timo observed high CPU load requested by EDS and indicator-datetime which indicates that these 2 services are clearly busy performing something in the background. As a result, when the clock app runs the tests after the calendar app, while saving the alarm, EDS does not respond to the clock resulting in the clock app crashing and causing the test to fail. Tomorrow morning I will test stopping the indicator- datetime and then running the tests again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321775 Title: High CPU usage observed across EDS and indicator-datetime causing clock app tests to fail To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
