Merge lp:~unity-team/unity8/launcher-sizing into lp:unity8
| Status: | Superseded | ||||
|---|---|---|---|---|---|
| Proposed branch: | lp:~unity-team/unity8/launcher-sizing | ||||
| Merge into: | lp:unity8 | ||||
| Prerequisite: | lp:~unity-team/unity8/launcher-updates | ||||
| Diff against target: |
1164 lines (+406/-110) 12 files modified
data/com.canonical.Unity8.gschema.xml (+11/-0) qml/Launcher/Launcher.qml (+33/-11) qml/Launcher/LauncherDelegate.qml (+8/-12) qml/Launcher/LauncherPanel.qml (+34/-34) qml/Shell.qml (+18/-1) qml/Stages/AbstractStage.qml (+2/-0) qml/Stages/DesktopStage.qml (+14/-11) qml/Stages/WindowResizeArea.qml (+3/-2) tests/mocks/GSettings.1.0/fake_gsettings.cpp (+64/-0) tests/mocks/GSettings.1.0/fake_gsettings.h (+18/-0) tests/qmltests/Launcher/tst_Launcher.qml (+110/-26) tests/qmltests/tst_Shell.qml (+91/-13) |
||||
| To merge this branch: | bzr merge lp:~unity-team/unity8/launcher-sizing | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Lukáš Tinkl (community) | 2016-02-17 | Approve on 2016-02-22 | |
| Albert Astals Cid (community) | 2016-02-17 | Abstain on 2016-02-22 | |
| PS Jenkins bot | continuous-integration | 2016-02-17 | Needs Fixing on 2016-02-19 |
| Unity8 CI Bot | continuous-integration | 2016-02-17 | Needs Fixing on 2016-02-19 |
| Daniel d'Andrada | 2016-02-17 | Pending | |
| Michał Sawicz | Pending | ||
| Michael Terry | 2016-02-17 | Pending | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2015-12-10.
This proposal has been superseded by a proposal from 2016-02-25.
Commit Message
Make launcher scalable, allow it locking
Description of the Change
* Are there any related MPs required for this MP to build/function as expected? Please list.
- see prereq
* 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?
y
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
n/a
* If you changed the UI, has there been a design review?
y
| Lukáš Tinkl (lukas-kde) wrote : | # |
Some tests failing:
qmltestrunner.
qmltestrunner.
qmltestrunner.
| Lukáš Tinkl (lukas-kde) wrote : | # |
One minor comment inline, fix the gsettings description
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2066
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2068
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2069
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in tests/qmltests/
1 conflicts encountered.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2071
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://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2073
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://
| Michael Terry (mterry) wrote : | # |
I know this may be bending too far backwards, but have you considered re-using the unity7 gsettings locations for the launcher?
The org.compiz.
I know it's cleaner to use our own schema. But compatibility between the two DEs (both of which we make!) would be nice. But I'm not going to push very hard for it. :)
===
In Launcher.qml, when lockedVisible changes, this code immediately calls hide(). Do you want to trigger the dismiss timer instead? That way panel.preventHiding gets respected. And just calling hide() assumes that lockedVisible is tied to autohideEnabled. Which it is... But feels weird to have those be overlapping states and have Shell.qml be the one combining them.
How would you feel about renaming lockedVisible to something like visibleByDefault and just having it be set to "scenario == desktop"? And then having Launcher combine that state and autohideEnabled to do the right thing.
The current way is fine too. But maybe just use the dismiss trigger instead of hide() at least.
===
I also tested this on my phone and couldn't pull the launcher out. It just didn't come out when I swiped from the left... I probably did something wrong... Maybe I should do a fresh build, I just moved qml files into place (no c++ changes here or in pre-req, right?) since the debs from jenkins are 404 now. Have you tested this MP recently?
| Michael Terry (mterry) wrote : | # |
Oh, duh. The gsettings schema. Need to make a deb I guess.
| Michael Terry (mterry) wrote : | # |
OK... Now I see that autohideLauncher is in fact a separate property from Launcher.
| Michael Terry (mterry) wrote : | # |
Maybe move the launcherSettings object into the main Shell object instead of the Launcher, since it is not a launcher-specific object?
The old GSettings object seems to have moved into a Unity8Settings override-able object on the OrientedShell... I guess someone figured that was easier to mock than our existing GSettings mocks? But that means it's not accessible from the base Shell now, hence why you needed to add your own GSettings object.
:(
===
Neither the pips nor the badge text changes size with the launcher icons. Is that intentional?
===
I'm getting "Damper::maxDelta must be a positive number. Aborted" when running xvfbtestLaunche
| Michael Zanetti (mzanetti) wrote : | # |
re re-using the unity7 schema: I did try to keep compatibility in the launcher for a long time. However, given the drastic changes of how we work with app ids now, at some point I could not reuse the favorites key in there any more. Also this branch's requirements were quite different at some point, in a sense that we'd need to store different size configs for different usage modes, this might come back as a design request at any point. Last but not least, the px vs GU issue is another one why I think reusing is not the best idea. Even if I'd convert it, the setting is stored in pixels and will break if the use switches to a screen with different PX/GU.
===
re: hide() vs dismissTimer. using dismissTimer would cause the launcher to wait for some seconds before hiding when the user changes the setting in systemsettings, which I think would be a bit weird (unity7 hides it immediately on setting change too). You do have a point that if the user would have the mouse hovered on the launcher while changing the setting it would hide despite the user "interacting" with it. However, is it really a use case that the user interacts with the mouse on the launcher and uses, touch or cmdline to make the launcher hide at the same time? Hence my decision to go for hide() immediately, so the user gets immediate feedback when clicking on the (yet to be added in settings) checkbox.
===
re requiring a .deb for testing. I usually copy the schema to the device and call "sudo glib-compile-
===
re moving GSettings around, yes, Daniel keeps on moving those things so he can mock them in QML instead of using the GSettingsController to control the mock... I think we should remove the Unity8Settings again, given that the only thing that we actually mock with that are already supported by our GSettingsContro
Anyhow, I've moved the GSettings object out of the launcher now and called it settings.
===
re pip and count emblems not scaling, yes, intentional. You couldn't read them any more at the smalles level and they'd be super huge on the biggest. I talked with design about that. we agreed to not scale them.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2075
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://
| Michael Terry (mterry) wrote : | # |
Alright then, sounds sensible. :)
I like the code changes, but looks like we have new failures in testShell at least? I get 15 new failures locally.
| Michael Zanetti (mzanetti) wrote : | # |
fixed the tests.
Please note that I had to merge lp:~dandrader/unity8/fixDragHandleTest in order to make xvfbtestShell work at all. As I already have a prereq, that diff will show up here too. It should vanish after the next landing.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2078
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://
| Michael Terry (mterry) wrote : | # |
I also see a failure in tst_Launcher:
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2079
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://
| Michael Terry (mterry) wrote : | # |
Hrm. Jenkins failure went away... And I can't see it locally, so fine. :) Approved, thanks!
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in qml/Launcher/
Text conflict in qml/Launcher/
2 conflicts encountered.
Was already top approved.
| Michael Zanetti (mzanetti) wrote : | # |
> Text conflict in qml/Launcher/
> Text conflict in qml/Launcher/
> 2 conflicts encountered.
>
> Was already top approved.
merged
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2080
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2080
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
Looks good again, and CI bot says good!
| Albert Astals Cid (aacid) wrote : | # |
Something went wrong
file://
| Lukáš Tinkl (lukas-kde) wrote : | # |
Found a small bug:
1. Alt+F1 to open the keyboard navigation
2. Press Down to highlight an item
3. Press Right to open the quicklist
4. Launch the app
5. The (keyboard) focus ring doesn't go away
| Michael Terry (mterry) wrote : | # |
That's probably a bug in the pre-req: https:/
| Lukáš Tinkl (lukas-kde) wrote : | # |
Hmm yes and no, it becomes obvious here now that the launcher stays locked visible in the desktop mode; tbh I don't recall seeing this when testing just the launcher-updates branch before
| Lukáš Tinkl (lukas-kde) wrote : | # |
When switching between windows with Alt+Tab (while the launcher is locked visible), the launcher flashes/flickers
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2081
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
> Found a small bug:
>
> 1. Alt+F1 to open the keyboard navigation
> 2. Press Down to highlight an item
> 3. Press Right to open the quicklist
> 4. Launch the app
> 5. The (keyboard) focus ring doesn't go away
> review: Needs Fixing
> Reply
> Michael Terry (mterry) wrote 1 minute ago: #
> That's probably a bug in the pre-req: https:/
> /+merge/278567
Indeed, fixed in the prereq and merged this
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2081
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: 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://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2082
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2083
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Lukáš Tinkl (lukas-kde) wrote : | # |
When having a fullscreen app (like camera or a webbrowser windows), the launcher should imho hide regardless of the visible-locked preference, just like the top panel does.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2083
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
FAILURE: 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://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2084
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2084
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2085
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
> When having a fullscreen app (like camera or a webbrowser windows), the
> launcher should imho hide regardless of the visible-locked preference, just
> like the top panel does.
done
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2085
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2086
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Lukáš Tinkl (lukas-kde) wrote : | # |
The flickering and fullscreen is fixed, great
| Lukáš Tinkl (lukas-kde) wrote : | # |
Please remove the spurious bzr tags, otherwise no more objections
| Michael Zanetti (mzanetti) wrote : | # |
> Please remove the spurious bzr tags, otherwise no more objections
done. must've been merged in after the initial proposal
| Lukáš Tinkl (lukas-kde) wrote : | # |
LGTM, works fine now, minus some some havoc in LauncherModel (unrelated to this branch), gonna file a bug about it
* 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 (all the relevant tests passing locally)
* Did you make sure that the branch does not contain spurious tags?
Yes
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2086
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2086
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2086
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2086
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Albert Astals Cid (aacid) wrote : | # |
Note: this was already top approved, re-approve after merge
Text conflict in qml/Components/
Text conflict in qml/Launcher/
Text conflict in tests/qmltests/
3 conflicts encountered.
| Michał Sawicz (saviq) wrote : | # |
I don't think "always-launcher" is as easy as resizing the desktop stage, it results in fullscreen^W apps moving about:
Non-fullscreen apps should probably get margins instead of the whole stage being moved about.
I'd vote for leaving the always-launcher feature out from this MP.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2089
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2089
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://
| Michael Terry (mterry) wrote : | # |
- panel.dismissTi
+ dismissTimer.
Is that right?
| Lukáš Tinkl (lukas-kde) wrote : | # |
qml/Launcher/
| Daniel d'Andrada (dandrader) wrote : | # |
Why to we need this new intermediate (id: stageContainer) Item in DesktopStage.qml?
| Michael Zanetti (mzanetti) wrote : | # |
> Why to we need this new intermediate (id: stageContainer) Item in
> DesktopStage.qml?
because the area for the apps needs to be smaller when the launcher is always visible. that said, this might not be good enough yet.
| Michael Zanetti (mzanetti) wrote : | # |
> - panel.dismissTi
> + dismissTimer.
>
> Is that right?
> qml/Launcher/
bad merge, thanks. fixed
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2090
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:2090
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://
| Daniel d'Andrada (dandrader) wrote : | # |
On 10/02/2016 14:31, Michael Zanetti wrote:
>> Why to we need this new intermediate (id: stageContainer) Item in
>> DesktopStage.qml?
> because the area for the apps needs to be smaller when the launcher is always visible. that said, this might not be good enough yet.
But the leftMargin is not being applied to it, but to appContainer instead.
| Michael Zanetti (mzanetti) wrote : | # |
> On 10/02/2016 14:31, Michael Zanetti wrote:
> >> Why to we need this new intermediate (id: stageContainer) Item in
> >> DesktopStage.qml?
> > because the area for the apps needs to be smaller when the launcher is
> always visible. that said, this might not be good enough yet.
>
>
> But the leftMargin is not being applied to it, but to appContainer instead.
Right. So the inner container is for the margins. As the wallpaper can't have the same margins (it shines through the launcher), it can't be inside that container. The outer is used for snapshotting the whole thing in order to apply blur for the spread background. I guess we could make the background also act as the outer container and with that get rid of one item. Anyways, as I said, this doesn't seem to be good enough for switching between fullscreen and non-fullscreen apps yet. have to rework it a bit.
| Lukáš Tinkl (lukas-kde) wrote : | # |
Yes, works good now, even with the spread and fullscreen apps
* 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 (all the relevant tests passing locally)
* Did you make sure that the branch does not contain spurious tags?
Yes
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2091
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:2091
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:2092
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:2092
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://
Unmerged revisions
- 2092. By Lukáš Tinkl on 2016-02-19
-
merge prereq
- 2091. By Michał Sawicz on 2016-02-17
- 2090. By Michael Zanetti on 2016-02-17
-
merge prereq
- 2089. By Michael Zanetti on 2016-02-17
-
don't resize the whole stage, instead add margins to non fullscreen things
- 2088. By Michael Zanetti on 2016-02-17
-
merge trunk
- 2087. By Michael Zanetti on 2016-02-12
-
merge prereq

FAILED: Continuous integration, rev:2065 jenkins. qa.ubuntu. com/job/ unity8- ci/6911/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 5697 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- xenial- touch/326/ console jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/1622 jenkins. qa.ubuntu. com/job/ unity8- qmluitest- xenial- amd64/325 jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/1517 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/1517 jenkins. qa.ubuntu. com/job/ unity8- xenial- amd64-ci/ 324 jenkins. qa.ubuntu. com/job/ unity8- xenial- i386-ci/ 323 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-touch/ 4423 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 5710 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 5710/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 25935 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- xenial- touch/125/ console jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- xenial- armhf/325 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- xenial- armhf/325/ artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 25937
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/6911/ rebuild
http://