Even if the qtbase patches themselves would be correct and functioning well and they just happen to make Autopilot break, we can't let Autopilot regress so badly. Either there should be something more done to Qt or an Autopilot landing fixing the issues should be put to the same silo.
I ran some Autopilot testing last night and continuing a bit now . The two new patches do not fix the AP problems. As examples:
- Archive image (#145): system- settings: 0 AP failures
* UITK: 1-2 AP failures
* webbrowser-app: 1-2 AP failures
* calculator: 0 AP failures
* ubuntu-
- Image (#147) added with silo 018 (qtbase DBus patches) system- settings: 16 AP failures (only 1 run done)
* UITK: 7-8 failures (similar to earlier #145 + previous qtbase DBus fix build)
* webbrowser-app: 5-7 failures
* calculator: 2 failures
* ubuntu-
Details at http:// people. canonical. com/~tjyrinki/ qt5/fail/ qtbase_ ubuntu5/
Even if the qtbase patches themselves would be correct and functioning well and they just happen to make Autopilot break, we can't let Autopilot regress so badly. Either there should be something more done to Qt or an Autopilot landing fixing the issues should be put to the same silo.
As for libusermetrics, the diff for its landing in #106 is at http:// launchpadlibrar ian.net/ 198152771/ libusermetrics_ 1.1.1%2B14. 10.20141020- 0ubuntu1_ 1.1.1%2B15. 04.20150219- 0ubuntu1. diff.gz