Merge lp:~josharenson/unity8/location_page_test into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Albert Astals Cid on 2015-07-20 |
| Approved revision: | 1795 |
| Merged at revision: | 1870 |
| Proposed branch: | lp:~josharenson/unity8/location_page_test |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~josharenson/unity8/settings_wizard_tests |
| Diff against target: |
139 lines (+67/-9) 2 files modified
tests/autopilot/unity8/settings_wizard/__init__.py (+48/-5) tests/autopilot/unity8/settings_wizard/tests/test_settings_wizard.py (+19/-4) |
| To merge this branch: | bzr merge lp:~josharenson/unity8/location_page_test |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Albert Astals Cid (community) | 2015-05-21 | Approve on 2015-07-20 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-07-17 | |
|
Review via email:
|
|||
Commit Message
Add handling for the location page to the autopilot settings wizard test
Description of the Change
* Are there any related MPs required for this MP to build/function as expected? Please list.
Yes. lp:~josharenson/unity8/settings_wizard_tests
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
- 1794. By Josh Arenson on 2015-05-21
-
Restore location file
- 1795. By Josh Arenson on 2015-05-21
-
Weird fu
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1795
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://
| Albert Astals Cid (aacid) wrote : | # |
How am i supposed to test this?
Running
autopilot3 run unity8.
I never get the location page, do i have to reset something? Shouldn't that reset be part of the autopilot test?
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1795
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://
| Albert Astals Cid (aacid) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
I could not, one is supposed to use the devel-proposed-
* Did CI run pass?
As much as it usually passes
* Did you make sure that the branch does not contain spurious tags?
Yes

FAILED: Continuous integration, rev:1795 jenkins. qa.ubuntu. com/job/ unity8- ci/5753/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- wily-touch/ 32 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- wily/16 jenkins. qa.ubuntu. com/job/ unity8- wily-amd64- ci/31 jenkins. qa.ubuntu. com/job/ unity8- wily-i386- ci/31 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- wily-mako/ 25 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- wily-armhf/ 32 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- wily-armhf/ 32/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 20697
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: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/5753/ rebuild
http://