Merge lp:~mterry/ubuntu-app-launch/look-at-mir into lp:ubuntu-app-launch
| Status: | Merged |
|---|---|
| Approved by: | Michael Terry on 2017-03-09 |
| Approved revision: | 291 |
| Merged at revision: | 299 |
| Proposed branch: | lp:~mterry/ubuntu-app-launch/look-at-mir |
| Merge into: | lp:ubuntu-app-launch |
| Prerequisite: | lp:~ted/ubuntu-app-launch/zg-ordering |
| Diff against target: |
438 lines (+124/-100) 5 files modified
libubuntu-app-launch/application-impl-snap.cpp (+61/-69) libubuntu-app-launch/application-impl-snap.h (+5/-11) tests/applications/qmlapp.desktop (+8/-0) tests/libual-cpp-test.cc (+24/-1) tests/list-apps.cpp (+26/-19) |
| To merge this branch: | bzr merge lp:~mterry/ubuntu-app-launch/look-at-mir |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| unity-api-1-bot | continuous-integration | 2017-02-16 | Approve on 2017-03-09 |
| Larry Price | 2017-02-16 | Approve on 2017-03-09 | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2017-02-14.
Commit Message
Use the "mir" interface (not the "unity8" interface) to decide if an app supports Mir or not.
Description of the Change
I know we were initially considering having the mir socket permissions in the unity8 interface. But they now live in the mir interface, so that's what we should pay attention to.
I left the "look at unity8 for lifecycle support" bits intact.
| Michael Terry (mterry) wrote : | # |
Hmm, I set this to WIP while I looked at the test failures. But I think they're all from the libertine moving target. I'll go back to Ready and just wait for that silo to land. Then see what CI says. This seems to be clear if I merge in the pending branches...
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
FAILED: Continuous integration, rev:289
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
FAILED: Continuous integration, rev:289
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
PASSED: Continuous integration, rev:289
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
- 290. By Michael Terry on 2017-03-09
-
Merge trunk
- 291. By Michael Terry on 2017-03-09
-
Add test for how trying to create non-graphical app Application object fails
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
PASSED: Continuous integration, rev:291
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/

FAILED: Continuous integration, rev:288 /jenkins. canonical. com/unity- api-1/job/ lp-ubuntu- app-launch- ci/227/ /jenkins. canonical. com/unity- api-1/job/ build/1680/ console /jenkins. canonical. com/unity- api-1/job/ build-0- fetch/1687 /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=amd64, release= xenial+ overlay/ 1462/console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=amd64, release= zesty/1462/ console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=armhf, release= xenial+ overlay/ 1462/console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=armhf, release= zesty/1462/ console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=i386, release= xenial+ overlay/ 1462/console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=i386, release= zesty/1462/ console
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /jenkins. canonical. com/unity- api-1/job/ lp-ubuntu- app-launch- ci/227/ rebuild
https:/