Merge lp:~dandrader/unity8/mouseEdgePush into lp:unity8
| Status: | Superseded |
|---|---|
| Proposed branch: | lp:~dandrader/unity8/mouseEdgePush |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~dandrader/unity8/cursorStartup |
| Diff against target: |
2832 lines (+1243/-372) 40 files modified
data/com.canonical.Unity8.gschema.xml (+16/-0) plugins/Cursor/MousePointer.cpp (+2/-0) plugins/Cursor/MousePointer.h (+4/-0) plugins/Utils/EdgeBarrierSettings.qml (+66/-0) plugins/Utils/qmldir (+1/-0) qml/Components/EdgeBarrier.qml (+111/-0) qml/Components/EdgeBarrierController.qml (+71/-0) qml/Components/PanelState/PanelState.qml (+3/-2) qml/Components/WindowControlButtons.qml (+76/-31) qml/Components/graphics/window-close.svg (+14/-0) qml/Components/graphics/window-maximize.svg (+12/-0) qml/Components/graphics/window-minimize.svg (+13/-0) qml/Launcher/Launcher.qml (+30/-32) qml/Launcher/LauncherPanel.qml (+7/-0) qml/Panel/Handle.qml (+2/-2) qml/Panel/Indicators/client/IndicatorsClient.qml (+1/-1) qml/Panel/IndicatorsMenu.qml (+11/-2) qml/Panel/MenuContent.qml (+1/-1) qml/Panel/Panel.qml (+68/-80) qml/Panel/PanelBackground.qml (+0/-21) qml/Shell.qml (+13/-0) qml/Stages/ApplicationWindow.qml (+29/-3) qml/Stages/DecoratedWindow.qml (+24/-16) qml/Stages/DesktopSpread.qml (+5/-19) qml/Stages/DesktopStage.qml (+107/-55) qml/Stages/SessionContainer.qml (+25/-1) qml/Stages/SurfaceContainer.qml (+56/-4) qml/Stages/WindowDecoration.qml (+15/-10) qml/Stages/WindowResizeArea.qml (+66/-21) tests/mocks/Cursor/Cursor.qml (+2/-0) tests/mocks/Unity/Application/MirSurface.cpp (+52/-0) tests/mocks/Unity/Application/MirSurface.h (+16/-0) tests/mocks/Utils/EdgeBarrierSettings.qml (+22/-0) tests/mocks/Utils/qmldir (+1/-0) tests/qmltests/EdgeBarrierControls.qml (+97/-0) tests/qmltests/Launcher/tst_Launcher.qml (+15/-5) tests/qmltests/Panel/tst_Panel.qml (+45/-11) tests/qmltests/Stages/tst_DesktopStage.qml (+96/-31) tests/qmltests/Stages/tst_WindowResizeArea.qml (+31/-12) tests/qmltests/tst_Shell.qml (+17/-12) |
| To merge this branch: | bzr merge lp:~dandrader/unity8/mouseEdgePush |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Zanetti (community) | 2015-10-30 | Approve on 2015-11-23 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-11-23 | |
| Albert Astals Cid (community) | merges fine | Abstain on 2015-11-20 | |
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2015-11-24.
Commit Message
Mouse has to push against edges to show launcher or apps spread
edge-barrier-
edge-barrier-
Description of the Change
* 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?
Not applicable
* If you changed the UI, has there been a design review?
John Lea tried it out. Values for the edge barrier parameters are still preliminary. Proper values will come once we have configurable mouse pointer speed and, most importantly, mouse pointer acceleration.
The graphical effect is following the design specification.
| Albert Astals Cid (aacid) wrote : | # |
There's a few qmluitests that fail to compile
| Daniel d'Andrada (dandrader) wrote : | # |
> There's a few qmluitests that fail to compile
Fixed.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2022
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://
- 2022. By Daniel d'Andrada on 2015-11-04
-
Use SDK 1.3 across all files Fixes: #1449628, #1503498, #1508363
Approved by: PS Jenkins bot - 2023. By Andrea Cimitan on 2015-11-04
-
Updated all 1.3 UbuntuShape to use new APIs where possible
Approved by: Albert Astals Cid - 2024. By Andrea Cimitan on 2015-11-04
-
Make zoomable and video playback widgets edge to edge
Approved by: Albert Astals Cid - 2025. By Andrea Cimitan on 2015-11-04
-
Add sharing widget to zoomable image and video playback
Approved by: Albert Astals Cid, Pawel Stolowski - 2026. By Albert Astals Cid on 2015-11-04
-
Make the scope settings list scroll to text visible area
Fixes: #1499084
Approved by: Michael Terry - 2027. By Albert Astals Cid on 2015-11-04
-
Move to importing QtQuick 2.4 & friends
This means we obviously require Qt 5.4 or greater, we had for a while
but make it official now
Approved by: Michael Terry - 2028. By Albert Astals Cid on 2015-11-04
-
Add an Item that proxies for old and new audio roles Fixes: #1493851
- 2029. By Michael Zanetti on 2015-11-04
-
Fixes for the panel buttons
* Hide panel buttons when switching to staged mode
* properly save/restore window states, not just geometry Fixes: #1431566, #1443319, #1504269, #1510360
Approved by: Lukáš Tinkl - 2030. By Michał Sawicz on 2015-11-04
-
Enable support for overriding application orientations based on device type Fixes: #1478637
- 2031. By Michael Terry on 2015-11-04
-
Handle lifecycle policy exceptions ourselves, instead of letting qtmir do it for us and allow non-Touch apps to opt-out of the Touch lifecycle.
This requires using the new isTouchApp unity-api property to ApplicationInfo
Interface. Now that qtmir won't decide policy for suspending exemptions anymore, we take over the interpretation of the lifecycleException GSettings key. Since the GSettings key for that was registered under the qtmir namespace (and there's no technical reason to migrate settings), I left the schema in qtmir itself. We merely consume it.
- 2032. By Michał Sawicz on 2015-11-04
-
Support server->client visibility change to stop rendering (lp:#1475678) Fixes: #1475678
Approved by: Daniel d'Andrada - 2033. By Christopher Lee on 2015-11-04
-
Quick spelling fix in process control output.
Approved by: Albert Astals Cid - 2034. By Albert Astals Cid on 2015-11-04
-
CroppedImageMin
imumSourceSize: Fix 'Binding loop detected for property "imageAspectRatio"' Approved by: Gerry Boland, Michał Sawicz
- 2035. By Michael Terry on 2015-11-04
-
Avoid showing the shutdown dialog when turning on the screen if your device is under heavy load.
Specifically, we actually watch the timestamp of input events as they come in to determine how long it's been. This means that if for whatever reason, processing of events get delayed, we don't misinterpret user input.
To test this, try running the following command and then turning the screen on and off again:
sudo cpulimit -l 1 -c 1 -p `ps ax | grep dbus-daemon | head -n 1 | awk '{print $1;}'`Without this branch, you'll notice that at some point, you see the shutdown dialog in error. Because unity8 couldn't keep up with events and thought 2s passed between power-pressed and power-released events.
But if we watch the timestamps, we can avoid that particular fate. Fixes: #1508563
Approved by: Albert Astals Cid, Michael Zanetti - 2036. By CI Train Bot Account on 2015-11-04
-
Releasing 8.11+16.
04.20151104- 0ubuntu1
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2023
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://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2026
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in tests/qmltests/
1 conflicts encountered.
| Michael Zanetti (mzanetti) wrote : | # |
Hmm... curious why we need 3 settings for this. Wouldn't one be enough? For instance, sensitivity, going from 0 to 100, which defines the grid units to be pushed... You probably do have a reason for this, what is it?
========
The shadow on the right edge looks very wrong. And I have a feeling it's too strong on the left edge too. You sure someone from design saw this? I know John didn't so far.
====
+ anchors.top: {
+ if (edge == Qt.LeftEdge || edge == Qt.RightEdge) {
+ return target.top;
+ } else {
+ return undefined;
+ }
+ }
writing this like this:
anchors.top: edge == Qt.LeftEdge || edge == Qt.RightEdge ? target.top : undefined
is quite a bit faster in evaluating. You should avoid adding JS blocks for bindings unless the other approach really ends up being unreadable.
======
+ // to be overwritten by tests
+ property bool _containsMouse: root.containsMouse
I'm starting to think you are mocking too much. Instead of all that logic with _containsMouse, wouldn't it be nicer to just use the standard containsMouse and in the test just do a mouseMove to fulfill that?
====
+ property real _defaultMinPush
+ property real _minPushThreshold:
+ property real _maxPushThreshold:
+ property real _accumulatedPush:
instead of all those _properties everywhere, didn't we agree to put them into private objects instead?
====
I feel like EdgeBarrierSettings isn't needed at all. The tiny bit of logic could happen in EdgeBarrier.qml too, and for mocking the settings, we already have a fully mocked GSettings backend in tests/mocks/
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 09:48, Michael Zanetti wrote:
> Review: Needs Fixing
>
> Hmm... curious why we need 3 settings for this. Wouldn't one be enough? For instance, sensitivity, going from 0 to 100, which defines the grid units to be pushed... You probably do have a reason for this, what is it?
>
It's explained in the commit message
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 09:48, Michael Zanetti wrote:
> + // to be overwritten by tests
> + property bool _containsMouse: root.containsMouse
>
> I'm starting to think you are mocking too much. Instead of all that logic with _containsMouse, wouldn't it be nicer to just use the standard containsMouse and in the test just do a mouseMove to fulfill that?
I've to mock this in order to *manually* test edge barriers. Can't do
otherwise. See EdgeBarrierCont
The automated tests do not overwrite this property and do the
mouseMove() just like you mentioned.
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 09:48, Michael Zanetti wrote:
> I feel like EdgeBarrierSettings isn't needed at all. The tiny bit of logic could happen in EdgeBarrier.qml too, and for mocking the settings, we already have a fully mocked GSettings backend in tests/mocks/
This is to avoid doing the same work several times. This settings stuff
is a singleton and thus is calculated/
can save several EdgeBarrier instances. So yes, we don't *need* to have
it separate, but it is more efficient that way.
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 09:48, Michael Zanetti wrote:
> The shadow on the right edge looks very wrong. And I have a feeling it's too strong on the left edge too. You sure someone from design saw this? I know John didn't so far.
The right edge and left edge shadows are the very same, just mirrored.
John Lea saw that (as I commented on the merge description). It puzzles
me to heard you say he did not...
By "wrong" you mean they're too opaque? Let's talk over IRC
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 08:09, Albert Astals Cid wrote:
> Text conflict in tests/qmltests/
> 1 conflicts encountered.
Fixed, thanks.
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 09:48, Michael Zanetti wrote:
> + property real _defaultMinPush
> + property real _minPushThreshold:
> + property real _maxPushThreshold:
> + property real _accumulatedPush:
>
> instead of all those _properties everywhere, didn't we agree to put them into private objects instead?
Done.
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 09:48, Michael Zanetti wrote:
> writing this like this:
>
> anchors.top: edge == Qt.LeftEdge || edge == Qt.RightEdge ? target.top : undefined
>
> is quite a bit faster in evaluating. You should avoid adding JS blocks for bindings unless the other approach really ends up being unreadable.
Isn't that Javascript all the same, but just in a more concise notation?
| Michael Zanetti (mzanetti) wrote : | # |
On 06.11.2015 14:12, Daniel d'Andrada wrote:
> On 06/11/2015 09:48, Michael Zanetti wrote:
>> writing this like this:
>>
>> anchors.top: edge == Qt.LeftEdge || edge == Qt.RightEdge ? target.top : undefined
>>
>> is quite a bit faster in evaluating. You should avoid adding JS blocks for bindings unless the other approach really ends up being unreadable.
>
> Isn't that Javascript all the same, but just in a more concise notation?
>
From http://
"There are two types of bindings in QML: optimized and non-optimized
bindings.
...
Things to avoid in binding expressions to maximize optimizability:
...
* constructing closures or defining functions within the binding expression"
If I understand that correctly, adding {} already breaks some optimizations.
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/11/2015 11:30, Michael Zanetti wrote:
>
> On 06.11.2015 14:12, Daniel d'Andrada wrote:
>> On 06/11/2015 09:48, Michael Zanetti wrote:
>>> writing this like this:
>>>
>>> anchors.top: edge == Qt.LeftEdge || edge == Qt.RightEdge ? target.top : undefined
>>>
>>> is quite a bit faster in evaluating. You should avoid adding JS blocks for bindings unless the other approach really ends up being unreadable.
>> Isn't that Javascript all the same, but just in a more concise notation?
>>
> >From http://
>
> "There are two types of bindings in QML: optimized and non-optimized
> bindings.
> ...
> Things to avoid in binding expressions to maximize optimizability:
> ...
> * constructing closures or defining functions within the binding expression"
>
> If I understand that correctly, adding {} already breaks some optimizations.
>
>
I think "{}" is a way of making scope explicit, not defining a closure
nor an internal function.
But thanks for the link. Bookmarked it. And as I said in a previous
comment, I made the change anyway as it does make the code cleaner
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2027
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:2029
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://
- 2039. By Launchpad Translations on behalf of unity-team on 2015-11-11
-
Launchpad automatic translations update.
- 2040. By Michael Terry on 2015-11-12
-
Make a few DBus calls asynchronous, for a smoother UX.
The calls I've changed here are neither hugely important nor frequent calls. But every little bit helps.
- Made a few sync calls async.
- Made a few sync calls more obviously sync. We had several instances of asyncCall()'s return value -- a QDBusPendingReply -- being assigned to a QDBusReply variable, which makes it wait for the call to finish. In cases where it didn't make sense to rewrite logic to be async, I've merely changed the method to be call() instead of asyncCall() for clarity.
- I removed the API in our AccountsService plugin for even making sync calls. This won't stop future developers from from writing sync code, but might give them pause.
- I removed some test mocks for our AccountsService plugin interface and changed those tests to use our actual AS plugin against a mock AS server. In truth, this change was because I had a devil of a time crafting a fake reply that included a custom complex type. But it's a good change anyway. Exercises more of our code in tests and reduces duplicated interfaces.
Approved by: Albert Astals Cid - 2041. By Daniel d'Andrada on 2015-11-12
-
Cursor: properly initialize hotspot position Fixes: #1510407
Approved by: Gerry Boland - 2042. By Albert Astals Cid on 2015-11-12
-
Warn we're using only the cache when not connected to the interwebs
Approved by: Michael Terry
- 2043. By Michael Zanetti on 2015-11-12
-
added icon for the dash Fixes: #1488146
Approved by: Albert Astals Cid, Lukáš Tinkl - 2044. By Daniel d'Andrada on 2015-11-12
-
Update GSettings mock in tst_OrientedShell
Gets rid of the following warning:
OrientedShell.qml:76: Error: Cannot assign to non-existent property "disableHeight"
Approved by: Albert Astals Cid - 2045. By Andrea Cimitan on 2015-11-12
-
Add sharing widget to zoomable image and video playback
Approved by: Albert Astals Cid, Pawel Stolowski - 2046. By Lukáš Tinkl on 2015-11-12
-
Restore windows when activating from the spread, maintain a focus stack
Stop displaying the "grabbing" icon when we merely click to focus the app's decoration.
Provide keyboard shortcuts for common window operations
Approved by: Michael Zanetti - 2047. By Michael Zanetti on 2015-11-12
-
prevent windows to be moved under the panel
If they happen to have a saved state which is under the panel
(might happen on alt+drag later), they will be moved below the panel
on close and reopen. This is how unity7 behaves in this regard. Fixes: #1438465
Approved by: Lukáš Tinkl - 2048. By Michael Zanetti on 2015-11-12
-
use UbuntuNumberAni
mations instead of linear ones for window state transitions Fixes: #1497097
Approved by: Lukáš Tinkl - 2049. By Albert Astals Cid on 2015-11-12
-
Make cardWidth and cardHeight real
If they are var the properties depending on them get reevaluated even if they don't change
Approved by: Michael Zanetti - 2050. By Michael Zanetti on 2015-11-12
-
update inputinfo api to the latest upstream snapshot
* Import latest update of api from gerrit.
* drop all the old mock code
* instead of mocking the whole api, add mocks for the backend only. This should simplify future updates and moving to upstream implementation a lot.
* update tests to use new mocking system
Approved by: Lukáš Tinkl - 2051. By Michael Zanetti on 2015-11-12
-
Add a warning dialog when disconnecting the external monitor.
In case there are still legacy apps running, the dialog forces the user to reconnect the external monitor, or close all the legacy apps.
Approved by: Daniel d'Andrada - 2052. By Albert Astals Cid on 2015-11-12
-
Reset instead of qFatal when removing things from the middle
This can be optimized but let's see how this behaves, at least we won't qFatal anymore :D Fixes: #1238979
Approved by: Andrea Cimitan - 2053. By CI Train Bot Account on 2015-11-12
-
Releasing 8.11+16.
04.20151112. 1-0ubuntu1
| Daniel d'Andrada (dandrader) wrote : | # |
Updated according to design spec.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2031
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://
- 2054. By CI Train Bot Account on 2015-11-20
-
Resync trunk.
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in qml/Stages/
Text conflict in tests/qmltests/
Text conflict in tests/qmltests/
3 conflicts encountered.
| Daniel d'Andrada (dandrader) wrote : | # |
> Text conflict in qml/Stages/
> Text conflict in tests/qmltests/
> Text conflict in tests/qmltests/
> 3 conflicts encountered.
Fixed.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2055
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 Zanetti (mzanetti) wrote : | # |
The jenkins test failure seems a real one. also, trying to run this on my laptop I get:
file://
Shell {
^
file://
^
file://
^
file://
^
file://
file://
property QtObject private: QtObject {
| Daniel d'Andrada (dandrader) wrote : | # |
> The jenkins test failure seems a real one. also, trying to run this on my
> laptop I get:
> [...]
Fixed.
Also fixed the problem in tst_Shell.qml
| Michael Zanetti (mzanetti) wrote : | # |
I'm still not 100% satisfied with the visuals. But I understand it's a lot of fiddling to tweak that further. I'm okay with doing that in a future branch. Let's land it.
All my other review comments have been addressed, so
* 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.
not yet, but issue has been fixed, let's see if next run passes.
* Did you make sure that the branch does not contain spurious tags?
yes
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2056
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
FAILURE: 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 Zanetti (mzanetti) wrote : | # |
I'm afraid at least some of the autopilot failures are related to the changes here. At least they passed today already on another branch (e.g. https:/
Can you please check them
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2057
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://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2056
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://
| Michael Zanetti (mzanetti) wrote : | # |
ok... seems that was a stale run above. jenkins looks ok now.
* 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.
on v+o it did, yes. x AP tests still busted.
* Did you make sure that the branch does not contain spurious tags?
yes
- 2057. By Daniel d'Andrada on 2015-11-24
- 2058. By Daniel d'Andrada on 2015-11-24
- 2059. By Daniel d'Andrada on 2015-11-24
-
Mouse has to push against edges to show launcher or apps spread
edge-barrier-
sensitivity is the property that should show up in the System Settings GUI. edge-barrier-
min-push and edge-barrier- max-push are exposed in GSettings merely as a
convenience so you can tweak those values without having to restart unity8. But they
should NOT show up in system settings. - 2060. By Daniel d'Andrada on 2015-11-26
-
Merge lp:~lukas-kde/unity8/newWindowDecosAndPanel again

FAILED: Continuous integration, rev:2021 jenkins. qa.ubuntu. com/job/ unity8- ci/6613/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 4954 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- xenial- touch/28/ console jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/1325 jenkins. qa.ubuntu. com/job/ unity8- qmluitest- xenial- amd64/28 jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/1220 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/1221 jenkins. qa.ubuntu. com/job/ unity8- xenial- amd64-ci/ 27 jenkins. qa.ubuntu. com/job/ unity8- xenial- i386-ci/ 27 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 3977 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 4951 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 4951/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 24761 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- xenial- mako/16/ console jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- xenial- armhf/28 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- xenial- armhf/28/ artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 24763
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: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/6613/ rebuild
http://