In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I9b5f826863fd913241cb803ef479b890f74fbb6c
Sphinx installs the package with its dependencies, but it does not use
the constraints. This can lead to errors if a dependency introduces any
backward incompatible changes. To avoid this the dependencies needs to
be installed prior to sphinx run by tox with the correct constraints.
Change-Id: I4ba83f1007dd11801b8e32c6d7566769e005480b
= six (and tox): the latest versions of tox (which are
compatible with newer virtualenv[1][2]) require a newer six.
[1] https://tox.readthedocs.io/en/latest/changelog.html#v3-14-4-2020-02-13
[2] https://github.com/tox-dev/tox/pull/1519
= alembic: A newer version is required by oslo-db 6.0.0.
= oslo.service: 1.24.0 (and before 1.31.0) capped eventlet to <0.21.0,
but eventlet>0.26.0 is now required.
= cryptography: paramiko 2.7.1 requires cryptography>=2.5.0
= oslo-messaging: bumped to 10.2.0
= greenlet: bumped to 0.4.16 to be compatible with py3.9
= warlock, amqp, pycodestyle: just drop those indirect dependencies
from l-c (and in fact pycodestyle is only a dependency of a linter
for testing).
Change-Id: I26bd73463a5da9ef947f287610b0a33b73062417
Python 3.8 is now our highest level supported python runtime.
This updates the default tox target environments to swap out
py37 for py38 to make sure local development testing is
covering this version.
This does not impact zuul jobs in any way, nor prevent local
tests against py37. It just changes the default if none is
explicitly provided.
Change-Id: I624c352b93e1bf5d8edea2db0feb7710e5b5e984
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Update local hacking checks for new flake8.
Note: The repo has been using an uncapped requirements, so was testing with
hacking 2.0 which disabled the old way of local testing integration.
Remove S367 and S368 since they are not working under python3
"NOTE(Kezar): This checks a good enough if we have only py2.7 supported.
As soon as we'll get py3.x we need to drop it or rewrite. You can read more
about it in dev-list archive, topic: "[hacking]proposed rules drop for 1.0"
Also, hacking now has H304 and H306 which test exactly the same.
Change-Id: I0b21554a5f9a69ed631b18c427b80c082011f774
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train. The correct zuul jobs are
already in place so this change just limits default 'tox' calls to py37
to save developers time.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Change-Id: I1d2cbec2b2f15ca1c6942947f369cf7192993a2d
Story: #2005924
Task: #34244
Requirements:
- bandit 1.6.0 contains a regression in the handling of patterns.
A fix is in place in bandit master, but newer versions introduces
more checks so they are not working as well.
The version is excluded there because is not handled by global
requirements.
Remove the separate requirement file for bandit, because
bandit has been part of test-requirements.txt in the last 3 years.
There is noneed for a separate requirements file anymore.
Even more, the bandit tox environment could be probably removed.
- synchronize the requirements for sphinx and jsonschema with the
current values from the requirements repository to make
the requirements-check job happy.
Jobs:
- temporarily disable the scenario-py3 job until a new stestr
(>2.3.1) is tagged.
Change-Id: Ief8e392fcd2d66a73593abcfda06fc7dbe2e53a6
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: If66a364be10271882629e0b278c8729172ff47bd
Depends-On: https://review.opendev.org/#/c/641878/
Thorough replacement of git.openstack.org URLs with their opendev.org
counterparts.
Depends-On: https://review.opendev.org/653988
Change-Id: I6c7fffc1a32cb35ff7fe2ba964510b4f32805842
It is wreaking havoc on the openstack gates, let's fix the issues.
Fix:
- E117: Over-indented code blocks;
- E305: Expected 2 blank lines after class or function definition
Ignore for now:
- W504: Line break after binary operator
- W605: Invalid escape sequence
W504 should be fixed together with its sibling W503.
Change-Id: I1483fae77153ffb24bfc51de2b83ea9db6737bfd
On the effort to make Sahara more user and operators friendly
we are splitting the plugins from Sahara core.
The main goal of this change is to facilitate installation,
maintainance and upgrade of plugins. With the plugins outside
the main Sahara code, operators will be able to install a subset
of plugins, as well as upgrade to newer versions of the plugins
without having to wait for a new version of OpenStack to be
released. As well, it aims to facilitate new contributors to
develop and maintain their own plugins.
Sahara Spec: https://specs.openstack.org/openstack/sahara-specs/specs/rocky/plugins-outside-sahara-core.html
Change-Id: I7ed0945fd82e37daaf6b29f947d3dba06db9d158
Also switch to pycodestyle from pep8 which requires a bump
of the the version of flake8 too.
Skip the following checks for now:
- E123 Closing bracket does not match indentation of opening bracket's line
- E226 Missing whitespace around arithmetic operator
- E402 Module level import not at top of file
- E731 Do not assign a lambda expression, use a def
- W503 Line break occurred before a binary operator
They should be probably revisited and fixed, if possible,
or skipped individually using # noqa
The following checks reported a limited number of errors and
they were fixed directly in this review:
- E241 Multiple spaces after ','
- E501 Line too long (82 > 79 characters)
Change-Id: I1f185d2efd1adf27a26e3ac93f2e1011c0b63124
This is a mechanically generated patch to add a unit test job running
under Python 3.6 as part of the python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ia9927693c1ef48e04b8eaa8d0754ce294f41cd97
Use the "modern" way of contraints setup and remove double setting of
constraints (in install_command and deps) for some environments.
Remove also -U from pip install command, it can break with constraints
and update required packages.
Change-Id: I2412a02dcba40a3128f9af766e27c046ce3d3f25
Use coverage+stestr for the cover tox target.
With this change, testrepository is not required anymore.
Change-Id: Ia294ee8003ccc10104f68777bea6921ff97bacef
According to Openstack summit session [1] stestr is
maintained project to which all Openstack projects
should migrate.
Let's switch it then.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Ic580dc7ba0684087a81137771fb125f4d412d948
Signed-off-by: Charles Short <zulcss@gmail.com>
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I03574b12fc9ef07ce459e81c9b8219a3b10bd4da
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The test does not work anymore with pip 10. For more details, see:
http://lists.openstack.org/pipermail/openstack-dev/2018-April/130027.html
(I suspect that the development that happened later in OpenStack testing
made it obsolete anyway).
Change-Id: I2227e70d23e5e7e99a85834ccc7d6ec8a09bf4ae
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I3a1d395b43e77010bf44ba71f5bcf146c01e0098
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This patch enable extensions:
-[H204] Use assert(Not)Equal to check for equality.
-[H205] Use assert(Greater|Less)(Equal) for comparison.
Change-Id: If1b09426deba024ce75ee0d2d687c2501a1e141d
Some of the available checks are disabled by default, like:
[H106] Don’t put vim configuration in source files
[H203] Use assertIs(Not)None to check for None
Change-Id: Ice7b791bf308ce9da047e2205a990b8d97924bd9
Each review which adds support for another plugin should change
the support matrix defined in the script.
Add the binary dependencies required for the sahara-image-pack
command.
Change-Id: Ibc294bd572ee4da298f125f9d9c4bff87ce5da9d
According to [1], we can passing a "-t" argument to
oslo_debug_helper to indicate the directory where tests
are located. This will solves ImportError exception.
[1] https://docs.openstack.org/developer/oslotest/features.html
Change-Id: I1b6b965f5e999aac85adf97ac7c0cb0a0edce41e
Closes-Bug: #1666560
With current os-api-ref and Sphinx 1.5, there were a couple of problems
in building api-ref: Wrong order of entries, wrong names.
Fix all so that api-ref builds again.
Also, tread warnings as errors for built so that no new problems get
introduced.
Change-Id: I6fbae3e93632472c60f848868b55cb7206ee76a9
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: Ifbe877705dbd87dea34d2b1974d2ae3ed7cac9a3
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: I15a761c0b6d5769b2dba9f521ef96cf43c99e552
Introduces a new libfuestfs-driven CLI for packing of
Sahara images, using the same recipe definition scheme
introduced in the validate-image-spi blueprint.
Documentation and plugin image packing configurability
can and will be provided in separate patches for ease
of review.
Partially-implements: blueprint image-generation-cli
Change-Id: I6788108e3fb6232045fc56937639a6348768a7bc