Merge lp:~aacid/unity8/make_try_no_cpu_usage into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michael Zanetti on 2015-05-28 |
| Approved revision: | 1793 |
| Merged at revision: | 1811 |
| Proposed branch: | lp:~aacid/unity8/make_try_no_cpu_usage |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~aacid/unity8/oxide_regression_workaround |
| Diff against target: |
20 lines (+2/-1) 1 file modified
tests/utils/modules/Unity/Test/UnityTestCase.qml (+2/-1) |
| To merge this branch: | bzr merge lp:~aacid/unity8/make_try_no_cpu_usage |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Zanetti (community) | 2015-05-27 | Approve on 2015-05-28 | |
| PS Jenkins bot | continuous-integration | 2015-05-27 | Approve on 2015-05-27 |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2015-05-27.
Commit Message
Bind running to the proper object.visible
The parent of that rotationAnimation is not the rotatingRectangle even if you'd expect it to be
Fixes continous CPU usage on make tryXXX
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?
Test change only
* 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?
No new warnings
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1792
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:1793
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

Yes!
* 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, sure it will
* Did you make sure that the branch does not contain spurious tags?
yes