Public bug reported:
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.
** Affects: indicator-datetime
Importance: Undecided
Status: New
** Affects: qtorganizer5-eds (Ubuntu)
Importance: Undecided
Status: New
** Also affects: indicator-datetime
Importance: Undecided
Status: New
** Summary changed:
- High CPU usage observed across EDS and indicator-datetime causing tests clock
app tests to fail
+ High CPU usage observed across EDS and indicator-datetime causing clock app
tests to fail
** Description changed:
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.
--
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:
New
Status in “qtorganizer5-eds” package in Ubuntu:
New
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
--
Mailing list: https://launchpad.net/~unity-api-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~unity-api-bugs
More help : https://help.launchpad.net/ListHelp
