Merge lp:~aacid/unity8/dash_ranges_on_move into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michał Sawicz on 2015-01-13 |
| Approved revision: | 1546 |
| Merged at revision: | 1552 |
| Proposed branch: | lp:~aacid/unity8/dash_ranges_on_move |
| Merge into: | lp:unity8 |
| Diff against target: |
160 lines (+99/-2) 3 files modified
qml/Dash/GenericScopeView.qml (+30/-2) tests/qmltests/Dash/tst_DashContent.qml (+57/-0) tests/utils/modules/Unity/Test/UnityTestCase.qml (+12/-0) |
| To merge this branch: | bzr merge lp:~aacid/unity8/dash_ranges_on_move |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-01-13 | |
| Michał Sawicz | 2015-01-13 | Approve on 2015-01-13 | |
|
Review via email:
|
|||
Commit Message
Make sure changing a scope doesn't trigger creation/
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
| Michał Sawicz (saviq) wrote : | # |
Testing this manually (patched a live phone) and this doesn't seem to be doing what it advertises. I added some debug lines in onCompleted and onDestruction and I'm still getting a lot of those when switching scopes to the sides (and I can see stuttering, too).
What's also interesting is that I've seen at least a few destructions on startup, which we should avoid if at all possible.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1545
http://
Executed test runs:
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michał Sawicz (saviq) wrote : | # |
OK there was some misunderstanding, it does indeed keep the margins and caches static *while* swiping. The creations I was seeing were due to the plugin querying next-to-adjacent scopes.
This does, however, fix the case when all the scopes are already loaded and you're swiping between them.
| Michał Sawicz (saviq) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
Y
* Did CI run pass? If not, please explain why.
N, unstable tests :/
* Did you make sure that the branch does not contain spurious tags?
Y
- 1546. By Albert Astals Cid on 2015-01-13
-
Increase the busy loop a bit
Busy loops are nasty, but can't think of another way to test this at the moment
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1546
http://
Executed test runs:
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

This test fails for me:
119 + verify( compareArrays( buttons2, buttons));
I've looked at the arrays and buttons kept about twice (~1200) as many items as buttons2 (~600).
It seems like a timing issue - i.e. we're creating too many items on startup?