Collecting httpretty>=0.7.1 (from -r
/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci@2/test-requirements.txt
(line 2))
ERROR: Could not find a version that satisfies the requirement
httpretty>=0.7.1 (from -r
The error shows:
ERROR: pylint: could not install deps [pylint==2.3.1,
-r/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci@2/test-requirements.txt];
v =
InvocationError('/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci@2/.tox/pylint/bin/pip
install pylint==2.3.1
Review: Approve continuous-integration
PASSED: Continuous integration, rev:2cc6cb72f0360fdd47f34e621433eee484bee869
https://jenkins.ubuntu.com/server/job/cloud-init-ci/699/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu
Review: Needs Fixing continuous-integration
FAILED: Continuous integration, rev:91576dc9e9c70c384272a0ffb9f6a20087b4a5f2
https://jenkins.ubuntu.com/server/job/cloud-init-ci/700/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
The proposal to merge ~smoser/cloud-init:fix/1788915-vlan-sysconfig-rendering
into cloud-init:master has been updated.
Description changed to:
For reference:
[1] documentes that no TYPE is present in the vlan examples.
[2] shows that random names are officially not supported.
[1]
Scott Moser has proposed merging ~smoser/cloud-init:fix/no-tox-yaml-warnings
into cloud-init:master.
Commit message:
git tests: no longer show warning about safe yaml.
Currently on 18.04, running tox -e py27 will spew errors like:
.tests/unittests/test_net.py:2649: YAMLLoadWarning: calling
Scott Moser has proposed merging
~smoser/cloud-init:fix/1788915-vlan-sysconfig-rendering into cloud-init:master.
Commit message:
network: Fix type and respect name when rendering vlan in sysconfig.
Prior to this change, vlans were rendered in sysconfig with
'TYPE=Ethernet', and incorrectly
I didn't know about the freshport patches until you mentioned that in your
previous comment. I'm not that familiar with FreeBSD. Anyway, I haven't see any
PR with these patches, but some of them are actually already covered by
branches.
--
I've a unittest to verify the path we're interested in here:
http://paste.ubuntu.com/p/PpMFn92CwV/
Please apply that to you branch.
--
https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/366329
Your team cloud-init commiters is requested to review the proposed merge of
sorry i somehow missed your answer. can not subscribe to this thread somehow.
can you subscribe me as branch owner?
it is ok to have a vanilla way to install the software. it just needs to be
maintained.
and independent of this: we should bring the freshport patches somehow upstream
and
This is what I've done in terms of testing:
```
lxc launch ubuntu:b c1
lxc file push *.snap c1/tmp/
lxc exec c1 /bin/bash
snap install /tmp/*.snap
/snap/bin/cloud-init clean --logs
/snap/bin/cloud-init init --local
/snap/bin/cloud-init init
```
http://paste.ubuntu.com/p/TXrh2n4mpk/ is
The proposal to merge ~jasonzio/cloud-init:requestMountAll into
cloud-init:master has been updated.
Commit message changed to:
cc_mounts: check if mount -a on no-change fstab path
Under some circumstances, cc_disk_setup may reformat volumes which already
appear in /etc/fstab (e.g. Azure
12 matches
Mail list logo
