Merge lp:~mterry/unity8/relock-during-tutorial into lp:unity8
| Status: | Rejected |
|---|---|
| Rejected by: | Michael Terry on 2016-03-24 |
| Proposed branch: | lp:~mterry/unity8/relock-during-tutorial |
| Merge into: | lp:unity8 |
| Diff against target: |
282 lines (+63/-47) 9 files modified
qml/Greeter/Greeter.qml (+14/-7) qml/Shell.qml (+2/-2) qml/Tutorial/TutorialContent.qml (+1/-0) qml/Tutorial/TutorialLeft.qml (+5/-3) qml/Tutorial/TutorialLeftFinish.qml (+5/-0) tests/qmltests/Greeter/tst_Greeter.qml (+7/-1) tests/qmltests/Tutorial/tst_Tutorial.qml (+9/-5) tests/qmltests/tst_Shell.qml (+20/-7) tests/qmltests/tst_ShellWithPin.qml (+0/-22) |
| To merge this branch: | bzr merge lp:~mterry/unity8/relock-during-tutorial |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Unity8 CI Bot | continuous-integration | Needs Fixing on 2016-03-24 | |
| Michał Sawicz | Needs Fixing on 2016-02-24 | ||
| PS Jenkins bot | continuous-integration | Needs Fixing on 2016-02-22 | |
| Albert Astals Cid (community) | 2016-02-10 | Approve on 2016-02-22 | |
|
Review via email:
|
|||
Commit Message
Don't keep greeter unlocked while tutorial is running, only while wizard is running. This lets you lock your screen again during the tutorial.
Description of the Change
This is a backported fix from the stuck-in-
- The Greeter.qml changes are to actually hide the lockscreen & greeter when forced to unlock. This makes sure it stays hidden even after the forcedUnlock hold is released. This also involves a UI change -- the cover page is no longer shown after the wizard. But that's desired by Design (part of the tutorial redesign). So I'm just pulling it forward a bit before the rest of the design:
https:/
- The Shell.qml changes are to allow the screen to be locked even though the tutorial is running (but still not when the wizard is running).
- The TutorialLeft.qml changes are to avoid the launcher being stuck in a pulled-out state when the greeter is locked during the tutorial.
* Are there any related MPs required for this MP to build/function as expected? Please list.
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
NA
* If you changed the UI, has there been a design review?
No, but it's a simple change requested by them.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2178
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
What's the reason for the changes in qml/Tutorial/
Also, lots of failing tests.
| Michael Terry (mterry) wrote : | # |
The reason for the TutorialLeft changes is that now that a user can lock the screen, if the launcher is bouncing out when the user locks it, it can get stuck that way (visible on lockscreen). This just makes sure that when the tutorial is paused (i.e. the lockscreen is up), we reset the animation to 0.
Failing tests due to this branch? I'll investigate and see what's up.
| Michael Terry (mterry) wrote : | # |
OK, I think I fixed the tests (they had previously used a user with a pin set which hadn't mattered since the lockscreen was skipped during the tutorial, but now it does matter, so I switched to a user without a pin).
Plus, I fixed one test and some logic to keep the animation correctly paused while a user drags the launcher.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2179
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: 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:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2179
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michael Terry (mterry) wrote : | # |
OK, pulled a little bit more from the tutorial-redesign, in order to fix the rest of the tests and keep internal Greeter state more consistent after the wizard closes.
See the MP description for a bit more explanation of the changes.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2180
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2180
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2181
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: 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:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2181
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
If i lock the screen after doing the pull of the launcher i.e. in the "There are the shortcuts to favorite apps" step, the launcher is not shown after unlokcing, i guess we should fix this? What do you think?
| Michael Terry (mterry) wrote : | # |
Great point, didn't notice that. Fixed in this branch by re-showing the launcher in this case.
May look *slightly* odd to see it animating in, but it looked better to me than instantly showing it on the screen. And (a) this whole tutorial is temporary, to be replaced soon and (b) this is an odd case.
So I didn't feel like optimizing.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2182
https:/
Executed test runs:
SUCCESS: https:/
UNSTABLE: https:/
SUCCESS: https:/
SUCCESS: https:/
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:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2182
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
Yes
* Did CI run pass? If not, please explain why.
Yes
* Did you make sure that the branch does not contain spurious tags?
Yes
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2183
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
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:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2183
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michał Sawicz (saviq) wrote : | # |
This breaks:
unity8.
https:/
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in qml/Greeter/
Text conflict in qml/Tutorial/
Text conflict in qml/Tutorial/
Contents conflict in qml/Tutorial/
Text conflict in tests/qmltests/
5 conflicts encountered.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2183
https:/
Executed test runs:
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
Oh, we don't need this anymore, since tutorial-redesign landed. I'll mark this MP rejected.
Unmerged revisions
- 2183. By Michael Terry on 2016-02-22
-
Merge from trunk
- 2182. By Michael Terry on 2016-02-17
-
Show launcher in LeftFinish screen after a lock/unlock
- 2181. By Michael Terry on 2016-02-12
-
Fix whitespace
- 2180. By Michael Terry on 2016-02-12
-
Actually tear down greeter when force unlocked (to keep it unlocked until shown)
- 2179. By Michael Terry on 2016-02-11
-
Fix tests
- 2178. By Michael Terry on 2016-02-10
-
Allow re-locking screen even if tutorial is running

FAILED: Continuous integration, rev:2178 /unity8- jenkins. ubuntu. com/job/ lp-unity8- 1-ci/311/ /unity8- jenkins. ubuntu. com/job/ build/432/ console /unity8- jenkins. ubuntu. com/job/ build-0- fetch/455 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 473 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial/ 473 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 469 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 469/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial/ 469/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 469 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 469/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial/ 469/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 469 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 469/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial/ 469/console
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: 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: /unity8- jenkins. ubuntu. com/job/ lp-unity8- 1-ci/311/ rebuild
https:/