We were able to reproduce the bug when the calendar and clock app were not isolated when running the AP tests. However nskaggs's branch attached to this bug report isolates the calendar app tests to its own environment. That could probably be why you are not seeing the high CPU usage. While discussing this timo, we agreed that while the way to fix this bug would be to isolate the two apps, it is also important that indicator-datetime and the eds-plugin handle the high-cpu usages more gracefully.
I suppose one way for you to confirm this bug would be to try out older build of the clock and calendar. If however you feel that the app isolation is sufficient and a prerequisite, then this bug can be considered resolved. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
