Merge lp:~aacid/unity8/test_stubborn_flick into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michał Sawicz on 2015-03-18 |
| Approved revision: | 1660 |
| Merged at revision: | 1685 |
| Proposed branch: | lp:~aacid/unity8/test_stubborn_flick |
| Merge into: | lp:unity8 |
| Diff against target: |
53 lines (+15/-6) 3 files modified
tests/qmltests/Dash/Previews/tst_Preview.qml (+1/-3) tests/qmltests/Dash/tst_Dash.qml (+1/-3) tests/utils/modules/Unity/Test/UnityTestCase.qml (+13/-0) |
| To merge this branch: | bzr merge lp:~aacid/unity8/test_stubborn_flick |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michał Sawicz | 2015-03-10 | Approve on 2015-03-18 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-03-12 | |
|
Review via email:
|
|||
Commit Message
Test: More stubborn flick to the end
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?
No, test fix 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
| Michał Sawicz (saviq) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
Test passes.
* Did CI run pass? If not, please explain why.
AP unstable, 7 qml tests to be fixed after UITK landing
* Did you make sure that the branch does not contain spurious tags?
Y
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1659
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://
- 1660. By Albert Astals Cid on 2015-03-12
-
A bit of refactoring
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1660
http://
Executed test runs:
FAILURE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| 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.
It improved
* Did you make sure that the branch does not contain spurious tags?
Y

FAILED: Continuous integration, rev:1658 jenkins. qa.ubuntu. com/job/ unity8- ci/5404/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 1700 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/568 jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/569 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/569 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 1508 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 1698 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 1698/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 18694
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: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/5404/ rebuild
http://