Re-enable non-visual component exporting in autopilot-qt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Confirmed
|
Critical
|
Unassigned | ||
Autopilot Qt Support |
Triaged
|
Critical
|
Unassigned |
Bug Description
It seems all autopilot tests so far seem to fail when run with Qt 5.2. The test app seems to be starting but eventually the failure happens as shown in the attached simple test log (Friends app).
You can upgrade the device to Qt 5.2 currently with the following instructions: http://
I filed bug #1273720 against unity8 already yesterday, but it seems all AP tests tend to fail, so it's not unity8 specific.
The PPA (https:/
All fixes should be made so that both Qt 5.0.2 and Qt 5.2 continue to work, ie usage of #ifdef:s or similar constructions.
Changed in autopilot: | |
status: | New → Fix Released |
Changed in autopilot-qt: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Christopher Lee (veebers) |
summary: |
- autopilot/phablet-test-run does not seem to work with Qt 5.2 + Re-enable non-visual component exporting in autopilot-qt |
Changed in autopilot-qt: | |
status: | Confirmed → Fix Released |
The binding loop problem seen in messaging app is on the UI Toolkit side, bug #1204453 bumped now to Critical because it affects Qt 5.2 more.