unity-api-bugs team mailing list archive

[Nekhelesh Ramananthan <krnekhelesh@xxxxxxxxx>]

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 Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/1321775

Title:
  High CPU usage observed across EDS and indicator-datetime causing
  clock app tests to fail

Status in The Date and Time Indicator:
  Incomplete
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed

Bug description:
  We have been observing random clock app test failures in the qa
  dashboard in image #39 and onwards. On further investigation we were
  able to reproduce to consistently,

  1. Run the clock app tests. You will notice that they pass with the exception of 1 test.
  2. Run the calendar app tests now.
  3. Run the clock app tests again. Notice that there are about 5-6 test failures related to Alarms (EDS).

  Timo noticed high CPU usages of EDS and indicator-datetime after the
  calendar app test finished. Somehow the calendar app test create
  events which are then messing up clock app results.

  In the QA Dashboard, the clock app test failures are only noticed
  randomly. This is because the tests are not executed in the same order
  all the time. So sometimes if the calendar is run after the clock,
  then the clock app tests have a good time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1321775/+subscriptions