Merge lp:~dobey/unity-scope-click/more-harness-tests into lp:unity-scope-click
| Status: | Merged |
|---|---|
| Approved by: | dobey on 2015-06-22 |
| Approved revision: | 335 |
| Merged at revision: | 333 |
| Proposed branch: | lp:~dobey/unity-scope-click/more-harness-tests |
| Merge into: | lp:unity-scope-click |
| Prerequisite: | lp:~dobey/unity-scope-click/adt-int-tests |
| Diff against target: |
725 lines (+468/-98) 17 files modified
CMakeLists.txt (+1/-1) debian/tests/run-tests (+1/-1) tests/scope-harness/CMakeLists.txt (+1/-2) tests/scope-harness/applications/com.ubuntu.developer.webapps.webapp-amazon_webapp-amazon_1.0.10.desktop (+12/-0) tests/scope-harness/applications/com.ubuntu.dropping-letters_dropping-letters_0.1.2.2.67.desktop (+14/-0) tests/scope-harness/applications/dialer-app.desktop (+201/-0) tests/scope-harness/applications/webbrowser-app.desktop (+18/-0) tests/scope-harness/fake_click/click (+27/-0) tests/scope-harness/fake_click/info/com.ubuntu.developer.webapps.webapp-amazon (+18/-0) tests/scope-harness/fake_click/info/com.ubuntu.dropping-letters (+25/-0) tests/scope-harness/fake_responses/click-package-index/api/v1/departments/communication/index.json (+1/-0) tests/scope-harness/fake_responses/click-package-index/api/v1/package/com.ubuntu.developer.webapps.webapp-amazon (+1/-0) tests/scope-harness/fake_responses/click-package-index/api/v1/package/com.ubuntu.dropping-letters (+1/-0) tests/scope-harness/run-harness.sh (+50/-0) tests/scope-harness/tests/__init__.py (+82/-0) tests/scope-harness/tests/test_apps.py (+11/-12) tests/scope-harness/tests/test_store.py (+4/-82) |
| To merge this branch: | bzr merge lp:~dobey/unity-scope-click/more-harness-tests |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-06-23 | |
| Charles Kerr (community) | 2015-04-03 | Approve on 2015-06-22 | |
|
Review via email:
|
|||
Commit Message
Enable more integration tests.
Add a script for running the tests with modified environment.
Refactor tests to use shared base testcase for fake servers.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:331
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Francis Ginther (fginther) wrote : | # |
The jenkins armhf job is failing and leaving behind several process:
1234 20278 1 0 11:25 ? 00:00:16 /usr/lib/
1234 20373 1 0 11:25 ? 00:00:04 python3 -m testtools.run discover
1234 20375 1 0 11:25 ? 00:00:04 python3 -m testtools.run discover
1234 20377 1 0 11:25 ? 00:00:04 python3 -m testtools.run discover
1234 20379 1 0 11:25 ? 00:00:16 /usr/lib/
lsof indicates that the three "python3 -m testtools.run discover" processes are blocking the umount.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:333
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:334
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:332
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://

FAILED: Continuous integration, rev:329 /code.launchpad .net/~dobey/ unity-scope- click/more- harness- tests/+ merge/255211/ +edit-commit- message
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http:// jenkins. qa.ubuntu. com/job/ unity-scope- click-ci/ 578/ jenkins. qa.ubuntu. com/job/ unity-scope- click-vivid- amd64-ci/ 34/console jenkins. qa.ubuntu. com/job/ unity-scope- click-vivid- armhf-ci/ 34/console
Executed test runs:
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity- scope-click- ci/578/ rebuild
http://