Merge lp:~aacid/unity8/fix_indicators_update_state into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Nick Dedekind on 2015-07-03 |
| Approved revision: | 1797 |
| Merged at revision: | 1871 |
| Proposed branch: | lp:~aacid/unity8/fix_indicators_update_state |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~aacid/unity8/oxide_regression_workaround |
| Diff against target: |
46 lines (+8/-1) 3 files modified
qml/Panel/IndicatorsMenu.qml (+1/-1) tests/autopilot/unity8/indicators/__init__.py (+1/-0) tests/qmltests/Panel/tst_IndicatorsMenu.qml (+6/-0) |
| To merge this branch: | bzr merge lp:~aacid/unity8/fix_indicators_update_state |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | 2015-05-27 | Needs Fixing on 2015-07-15 |
| Nick Dedekind (community) | 2015-06-19 | Approve on 2015-07-03 | |
| Unity Team | 2015-05-27 | Pending | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2015-05-26.
Commit Message
Update state of indicators bar only when the user is actively dragging himself
Fixes race with timer causing bug 1457044
Description of the Change
* Are there any related MPs required for this MP to build/function as expected?
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?
N/A
* If you changed the UI, has there been a design review?
N/A
* Did you have a look at the warnings when running tests? Can they be reduced?
Yes, not introducing any new warning
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1794
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1795
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 1796. By Albert Astals Cid on 2015-06-22
-
Merge unity8
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1796
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Nick Dedekind (nick-dedekind) wrote : | # |
The change to the tests doesn't test the issue. If succeeds whether the change in IndicatorsMenu exists or not. You can test by updating unitProgress without having an active bar.
indicatorsMenu.
compare(
indicatorsMenu.
compare(
| Nick Dedekind (nick-dedekind) wrote : | # |
although unitProgess is a readonly.
can use:
indicatorsMenu.
indicatorsMenu.
- 1797. By Albert Astals Cid on 2015-07-03
-
Merge unit8
| Albert Astals Cid (aacid) wrote : | # |
> The change to the tests doesn't test the issue. If succeeds whether the change
> in IndicatorsMenu exists or not. You can test by updating unitProgress without
> having an active bar.
You are right, the change in the test is not to test the change, is to make it so that the test still works, did not feel the need to add a qmltest to check this is working since the autopilot test was already failing sometimes without this so we actually already have something that makes sure this is needed.
| Nick Dedekind (nick-dedekind) wrote : | # |
> > The change to the tests doesn't test the issue. If succeeds whether the
> change
> > in IndicatorsMenu exists or not. You can test by updating unitProgress
> without
> > having an active bar.
>
> You are right, the change in the test is not to test the change, is to make it
> so that the test still works, did not feel the need to add a qmltest to check
> this is working since the autopilot test was already failing sometimes without
> this so we actually already have something that makes sure this is needed.
ok, fine.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1797
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1797
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

FAILED: Continuous integration, rev:1793 jenkins. qa.ubuntu. com/job/ unity8- ci/5765/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- wily-touch/ 44 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- wily/28/ console jenkins. qa.ubuntu. com/job/ unity8- wily-amd64- ci/43 jenkins. qa.ubuntu. com/job/ unity8- wily-i386- ci/43 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- wily-mako/ 34 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- wily-armhf/ 44 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- wily-armhf/ 44/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 20734
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/5765/ rebuild
http://