Merge lp:~fginther/ubuntu-touch-boottest/add-vivid-support into lp:ubuntu-touch-boottest
Status: | Merged |
---|---|
Approved by: | Francis Ginther |
Approved revision: | 5 |
Merged at revision: | 5 |
Proposed branch: | lp:~fginther/ubuntu-touch-boottest/add-vivid-support |
Merge into: | lp:ubuntu-touch-boottest |
Diff against target: |
49 lines (+24/-2) 1 file modified
boottest.sh (+24/-2) |
To merge this branch: | bzr merge lp:~fginther/ubuntu-touch-boottest/add-vivid-support |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Paul Larson | Approve | ||
Francis Ginther | Needs Resubmitting | ||
Para Siva (community) | Approve | ||
Review via email: mp+261213@code.launchpad.net |
Commit message
Add support for a specific image per release and fail the test if the source package produces no needs-install binaries.
Description of the change
Add support for a specific image per release and fail the test if the source package produces no needs-install binaries.
Foundations (sil2100) has confirmed that these are the right images to use. Also checking to make sure the binaries installed on these images match the manifest which britney would use (see: https:/
This been tested:
* wily gtk+3.0 (valid wily package) - http://
* vivid gcc-5 (NOT a valid vivid package) - http://
* vivid gcc-4.9 (valid vivid package) - http://
* wily gcc-4.9 (NOT a valid wily package) http://
I think we should make a slight change to this for when the package has no binaries, but do you have an example of a case where that actually happens? It seems like if that were the case?