Merge ~smoser/cloud-init:pylint/1444-pylint-tip-ignore-e1101-from-contextlib into cloud-init:master
| Status: | Merged |
|---|---|
| Merged at revision: | 9c33cb24b8a834aa8034db4c989725901a0814c6 |
| Proposed branch: | ~smoser/cloud-init:pylint/1444-pylint-tip-ignore-e1101-from-contextlib |
| Merge into: | cloud-init:master |
| Diff against target: |
48 lines (+9/-2) 3 files modified
cloudinit/util.py (+3/-2) setup.py (+4/-0) systemd/systemd-fsck@.service.d/cloud-init.conf (+2/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Chad Smith | 2017-05-22 | Approve on 2017-05-22 | |
| Server Team CI bot | continuous-integration | Approve on 2017-05-22 | |
| Joshua Powers (community) | 2017-05-22 | Approve on 2017-05-22 | |
| cloud-init commiters | 2017-05-22 | Pending | |
|
Review via email:
|
|||
Commit Message
tox: move pylint target to 1.7.1
The motivation for this is to make tip-pylint target green.
It does 2 things:
a.) silence a warning that is generated in pylint 1.7.1, but not
other versions of pylint. This bug in pylint is filed at
https:/
b.) move tox -e pylint to use pylint 1.7.1
| Chad Smith (chad.smith) wrote : | # |
s/pylint-
| Joshua Powers (powersj) wrote : | # |
Why are there systemd changes at all? I am probably the last person who should comment on a merge request including more than what the change log says, but why are those necessary?
PASSED: Continuous integration, rev:8d00f6ae2e3
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:5e6cda86fe9
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
The systemd changes are not actually present.
They were a result of me being on a branch (https:/
They're not present any more, launchpad just isn't updating the diff that you see.
If you look at the commit
https:/
directly, you'll see the proper diff.
PASSED: Continuous integration, rev:b01ae962765
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:9c33cb24b8a
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
| Chad Smith (chad.smith) wrote : | # |
I think we agreed in standup that since you've fixed this with a workaround for pylint's bug, you could probably add a structured comment or something that mark that we should look at pylint tip in the future to see if that issue is fixed. For bugs on external dependencies which cloud-init expects to be fixed at some in the future, we probably should decide on a comment label or something if we need to revisit this logic in the future to clean it up or remove a workaround. (like # RELEASE_REVIEW or RELEASE_BLOCKER). Then we can have a simple grep to search for fixes or old external bugs we should double check upon next SRU.


PASSED: Continuous integration, rev:d6518ba988e 24f939687d83d59 46bb9a3ce2751a /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 367/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- amd64/367 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/367 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 367 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- s390x/367 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/367
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 367/rebuild
https:/