Merge lp:~cimi/unity8/fix-lazyImage-test-flakyness into lp:unity8
| Status: | Superseded |
|---|---|
| Proposed branch: | lp:~cimi/unity8/fix-lazyImage-test-flakyness |
| Merge into: | lp:unity8 |
| Diff against target: |
71 lines (+23/-6) 2 files modified
qml/Components/LazyImage.qml (+3/-0) tests/qmltests/Components/tst_LazyImage.qml (+20/-6) |
| To merge this branch: | bzr merge lp:~cimi/unity8/fix-lazyImage-test-flakyness |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Unity8 CI Bot | continuous-integration | Approve on 2016-01-13 | |
| Michael Zanetti (community) | 2015-11-13 | Needs Information on 2015-11-27 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-11-17 | |
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2016-01-28.
Commit Message
Should fix lazyimage test failures on fast machines
Description of the Change
* Are there any related MPs required for this MP to build/function as expected? Please list.
n
* Did you perform an exploratory manual test run of your code change and any related functionality?
y
* 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?
n/a
| Albert Astals Cid (aacid) wrote : | # |
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2040
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: 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:2040
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: 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://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2040
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 : | # |
that signal seems to be just used for testing. If so, can't we use "findInvisibleC
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2040
https:/
Executed test runs:
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
ok, had been looking at this and besides the fact that I cant repro the flakiness at all, it seems to me that the code actually properly does wait for the transition already.
If there's still some flakiness it's probably because of the render thread lagging a bit behind and I think a simple "waitForRenderi

Not sure this is the correct fix, as far as i see it the problem is that the state of the LazyImage when changing goes
qml: STATE default
qml: STATE ready
qml: STATE loading
qml: STATE ready
The first ready seems to be wrong to me.