This prepares to run the proposal bot to generate constraints on
python3.11 instead of python3.10. The actual job to run this will need
to be added in the project-config repo.
Change-Id: I8fe5f8fe335cccf9c9ce166e931c4a42d9d79457
Gating jobs started to fail with latest pyproject-api (1.6.1) release.
This release would need latest tox (4.11.0) to not fail, but we are
pinning tox via pinning virtualenv in tox.ini.
To resolve this we have to remove the virtualenv pinning, which was a
"temporary" hack to avoid py3*-check-uc jobs to break. This job is
failing because of ryu package, which is unmaintained and projects
started to use os_ken instead, which "is a fork of the Ryu library
tailored for OpenStack Neutron" [1]. Hence, this patch removes ryu
from requirements files to eliminate the need of pinning virtualenv.
[1] https://opendev.org/openstack/os-ken
Change-Id: I23ba892e6dd7f2566e5af6626c072c2dcc5a4382
Start checking requirements on python3.11 to get early warnings about
upcoming issues. Non-voting for now.
Change-Id: I7713029b95beb69d87f5cba66997fd4ba422c6b0
With latest virtualenv (and setuptools bundled in it) py3*-check-uc
jobs started to fail as pkg_resources' __getattr__ breaks on multiple
packages' metadata.
Release is very close and library release upper constraints bumping
patches are piling up. This patch is a workaround only to unblock the
gate and need to be reverted as soon as the py3*-check-uc jobs works
well with the latest virtualenv and setuptools releases.
Change-Id: I36ae32a401844bf5a5df0d20d3f88f24b2a0cf8e
tox.ini started failing with Tox4 which had some
incompatible changes. One of them is to allow
external command to run by adding them into allowlist_externals
Fixing tox.ini for tox4 changes.
Change-Id: I7bc7c98954395765f16cc943e5c826983db5dba0
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I8614a6a6d4db1c4994c7dea1fe4f4cb31bdfe25e
- auto detect python paths (which)
- make it possible to call `tox -e generate` w/o extra args
- update list of pythons to include currently supported versions
Change-Id: Ib727242c1aba8597389259d8dbacba7194f9f0d6
in I2598503c2d4397d7efbb03a76df9a4e91dd0c1cf we mistakenly added
constraints to install_command in out based testenv. This is incorrect
as it means the generate env will be run in a constrained environment.
We don't use UPPER_CONSTRAINT_FILE as *right now* it's the same thing
and this leaves us internally consistent (even if technically incorrect)
Change-Id: Ia61d944dbfdf494598e41e5fbefd0e32a91814ed
This adds the use of upper constraints in our tox environments. Jobs
like openstack-tox-py27 have started failing due to trying to install
lib versions that only support Python 3.
The 'generate' target keeps the unconstrained deps since we actually do
need the latest installed for that.
Updates the requirements-integration job to run using py36 since that
now fails with running under py27. This should get the job to pass until
we are able to rewrite it to not be a legacy job.
NOTE(dmllr): updated install_command to include local constraints file
Change-Id: I2598503c2d4397d7efbb03a76df9a4e91dd0c1cf
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Currently a safety check failure is ignored, the output
is just for informational purposes. it reports known
security issues with the versions in upper-constraints.txt
so that we can determine a corrective action.
Change-Id: Ib8191602f47641eb047ebe5972ffa92bcfd08de4
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: I6b493911d950182a9da1e13f01ef22e7bb0516b8
Currently as we have basepython set in the testenv we always get the
same python3 binary even when specifying a specific env (eg py37).
This change uses ignore_basepython_conflict to tell tox when creating
the py3X envoronments to use the major/minr from the env rather than
basepython.
Before:
[tony@thor requirements]$ tox -re py37,py35,py36,py27 --notest
[tony@thor requirements]$ for py in .tox/py*/bin/python ; do echo $py ; $py --version ; done
.tox/py27/bin/python
Python 3.6.6
.tox/py35/bin/python
Python 3.5.6
.tox/py36/bin/python
Python 3.6.6
.tox/py37/bin/python
Python 3.6.6
After:
[tony@thor requirements]$ tox -re py37,py35,py36,py27 --notest
[tony@thor requirements]$ for py in .tox/py*/bin/python ; do echo $py ; $py --version ; done
.tox/py27/bin/python
Python 2.7.15
.tox/py35/bin/python
Python 3.5.6
.tox/py36/bin/python
Python 3.6.6
.tox/py37/bin/python
Python 3.7.0
Change-Id: Ie16bfa0a96d41cc3d1712b0d3c7a6ce2378b5478
Set up a tox environment for running project-requirements-change.py,
the script used in the requirements-check job.
Change-Id: I5336222949acfd947f2ef54ed120e3632b28ccb7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Python 3.6 is installed by default in Ubuntu 18.04 LTS.
According to Python2 Deprecation Timeline [1] and Python3-first Goal [2],
we should have py36 testenv ready for it.
This change adds a non-voting job for checking the 3.6
upper-constraints, and a voting job for py36.
Once we're confident we have all the bits in place for 36-uc checking we
can promote that job to voting.
[1] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html
[2] https://review.openstack.org/#/c/575933
Change-Id: Ia06c1ab217e80902adb607a3bc6063aae66f48bf
Rely on our ability to compute a good lower constraints set for
multiple projects using the build-lower-constraints command instead of
maintaining a single list in this repository.
Change-Id: I0a4be42efdbfd73228d043c1aa21feb7829650f3
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update tox to use python3 for most jobs instead of python2. Leave
python2 in place where the job name clearly means for it to be used.
Change-Id: I7ecbae445de9641de0622af97f7ca9dff35b8066
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
When the TC merged I2637dd714cbb6d38ef8b8dc1083e359207118284 we're
supposed to invoke stestr rather than testr so lets do that
Change-Id: Ic5b984949462e9d96d0ba122531d7f0a3d733891
This is generated from the lower bounds of g-r.txt
and to be maintained manually. There is a variant
of check-uc called check-lc added that will verify
those dependencies to be coinstallable and passing
consistency checks.
Change-Id: I99ad9f0b1d6c150bee6d6d35f84a74e99ab849b8
Also keep pep8 as a compat wrapper around it, to be remove
once zuul config has been adjusted to run linters instead.
Change-Id: I1e1be5bd2cd5a3f6b1c0f68ccf29e536b1743311
With zuulv3, we are now using bindep.txt more to manage
build-wheel-jobs. As such, give an update to start supporting
centos-7. I've also cleaned up a few depedencies we no longer need.
This also add support to test wheel-mirror builds.
Change-Id: Ia6c1113d119b01e7189e4ada41e10865c4ec0066
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Listing hacking in test-requirements is deprecated, as
it is a blacklisted linter and the global requirements update
bot wouldn't update it anyway. Instead use it just as a
dep on the pep8 tox env.
Change-Id: Idb4bcd8e4ffe1738a7306f9e1e5530b7e1e8dc8f
These are going to be rewritten to native zuulv3 jobs
in the next commit.
Needed-By: I3b0dbdcc02a0a8cff0c52701fadf7632648afb97
Change-Id: I3b9a86528350242c4d785d0f49c318de6c29ec75
Add a bashate environment for checking shell code quality.
Exclude bashate warnings:
E006: Line too long:
E010: The "do" should be on same line as for
In my opinion the places that trip these do not impact code readability
Change-Id: Iab0a34542c3938f127515291eca8f027f3accaa0
Some of the dependencies may not be constrained on their own (pbr) so
use the constraints list to enforce the constraints.
Change-Id: I3ae5835d1b1b8f75608d7bb110732f9be233b13f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Implement XFAIL handling for ignoring known problems so that
we can make the job voting until the remaining issues are sorted
out.
Change-Id: Ia2cf2c440a72e6365a9ff08086704dc535bbc072
Due to the rename of the job adding the -ubuntu-xenial suffix,
we have exceeded the path limit and can no longer run inside the
tox environment. shortening to a shorter check name (and renaming
the job) should fix this.
Change-Id: I0927ae81148d15256bd4dfe2a5e48b1819bbe2af
This change creates a new tox environment that *only* installs
openstack_requirements and then verifies that each of the console
scripts has all of the modules that it imports.
This will need to be added to our gate RSN
Change-Id: Ibc37593afcc4d9f820cb88168e1aa15e773b2087
Use pkg_resources.require to report conflicts to ensure
co-installability.
Co-Authored-By: Igor Yozhikov <iyozhikov@mirantis.com>
Change-Id: I7443496b6a06d02bb9cc9457b729dea71451f44a
Dr. Jens Harbott