unity-api-bugs team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

I'm not able to reproduce the reported high CPU in indicator-datetime in
build 53.

Setup:
I took a phablet freshly flashed to build 53, ran phablet-click-test-setup on the desktop followed by "click-buddy --dir . --provision" in the root directories of ubuntu-clock-app and ubuntu-calendar-app.
On the phablet I tweaked the autopilot directory to allow the ubuntu-calendar-app's tests to run (see lp:~nskaggs/ubuntu-calendar-app/fix-ap-env-setup).
In a separate phablet-shell, "powerd-cli display on bright"
Finally, I was ready to run the tests: "phablet-test-run -v ubuntu_clock_app", "phablet-test-run -v calendar_app", and "phablet-test-run -v ubuntu_clock_app".

Results:

1. During the first run of clock-app's autopilot tests, indicator-
datetime's cpu stayed in the [0.0 .. 0.1%] range in htop and its
cumulative time went from 0:00.75 to 0:01.91, a cumulative time growth
of 1.16.

2. During the calendar-app autopilot tests, datetime's cpu use stayed in
the [0.0 .. 0.1%] range in htop and its cumulative time went from
0:01.91 to 0:02.08,.

3. During the second run of clock-app's autopilot tests, datetime's cpu
use stayed in the [0.0 .. 0.1%] range in htop and its cumulative time
went from 0:02.08 to 0:03.18, an increase of 1.10, which is fairly
consistent with the levels in the first test.

So nik90 or timo, if you're still able to reproduce this high CPU load
in indicator-datetime is there a chance you could provide some
information on either what steps I need to change to reproduce the
behavior, or (say) a cachegrind profile of indicator-datetime taken
during one of these high CPU sessions...

** Changed in: indicator-datetime
       Status: New => Incomplete

** Changed in: indicator-datetime
     Assignee: (unassigned) => Charles Kerr (charlesk)

-- 
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