Three consistent autopilot test failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity8 (Ubuntu) |
Fix Released
|
High
|
Nick Dedekind | ||
Vivid |
New
|
Undecided
|
Unassigned |
Bug Description
We seem to have stabilized on three tests failing repeatedly:
unity8.
unity8.
unity8.
Example run:
https:/
The two latency ones are relatively new tests, the lifecycle one seems to be a new consistent failure.
What's even more important is that they're reliably reproducible locally using the steps below:
http://
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity8 8.02+15.
ProcVersionSign
Uname: Linux 3.19.0-13-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 21 22:18:54 2015
SourcePackage: unity8
SystemImageInfo:
current build number: 0
device name:
channel: daily
last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Michael Zanetti (community): Needs Fixing
- Albert Astals Cid (community): Approve
-
Diff: 226 lines (+96/-20)3 files modifiedtests/autopilot/unity8/application_lifecycle/tests/test_application_lifecycle.py (+13/-3)
tests/autopilot/unity8/indicators/tests/test_action_latency.py (+4/-2)
tests/mocks/indicator-service/mock-indicator-service.c (+79/-15)
- Leo Arias (community): Disapprove
- Albert Astals Cid (community): Needs Fixing
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
-
Diff: 26 lines (+8/-2)1 file modifiedtests/autopilot/unity8/indicators/__init__.py (+8/-2)
- Albert Astals Cid (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Registry Administrators: Pending requested
-
Diff: 313 lines (+84/-57)3 files modifiedplugins/Ubuntu/Settings/Components/serverpropertysynchroniser.cpp (+60/-41)
plugins/Ubuntu/Settings/Components/serverpropertysynchroniser.h (+5/-2)
tests/qmltests/Components/tst_ServerPropertySynchroniser.qml (+19/-14)
I think I realized why the lifecycle test fails - the fake app in fixture is suspended as soon as it's launched (because screen is locked if you have a passcode/password, as we do on a phone provisioned with the CI script), and the following dbus introspection timeouts are from the app, not from unity8.