Merge ~smoser/cloud-init:bug/package-build-no-stylechecks into cloud-init:master
Status: | Merged |
---|---|
Merged at revision: | 6b5369be71054a677b89fa8080f7ddd029ce4986 |
Proposed branch: | ~smoser/cloud-init:bug/package-build-no-stylechecks |
Merge into: | cloud-init:master |
Diff against target: |
91 lines (+12/-18) 3 files modified
packages/debian/control.in (+0/-4) test-requirements.txt (+0/-6) tox.ini (+12/-8) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Joshua Powers (community) | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
cloud-init Commiters | Pending | ||
Review via email: mp+324541@code.launchpad.net |
Commit message
tox/build: do not package depend on style requirements.
When the style/checking dependencies were updated in
test-requiremen
by ./packages/bddeb were also updated. Pycodestyle was added to the list
in order to pin its version. That broke the package build for 16.04. The
reason for this is simply that python3-pycodestyle is not available in
16.04.
The change here is to remove style dependencies from test-requirements,
and add them to the tox environments directly. We had previously changed
the package build process to not run pep8 or flake8 simply to avoid having
to code to N different versions of style checkers (3bcb72c593f).
The link between package build and test-requirements still exists, though.
So future breakage can occur if any package is added to
test-requiremen
does not have a python3-
There is also a bit of a tox.ini cleanup here, in that we do not have to
explictly list '-rrequirements
lastly, we drop the -rtest-
add these test requirements only to environments that need to run test.
Finally, a change to packages/
dependencies that were listed for style checking and also a dependency
on iproute2 which was a bad unit test that has been previously fixed.
FAILED: Continuous integration, rev:e99f746105f c605e99eb792d3b 17dae9240c099a /code.launchpad .net/~smoser/ cloud-init/ +git/cloud- init/+merge/ 324541/ +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:/
https:/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 389/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- amd64/389/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/389/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 389/console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- s390x/389/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/389/ console
Executed test runs:
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 389/rebuild
https:/