diff options
| author | Tim Burke <tim.burke@gmail.com> | 2023-01-03 17:32:14 -0800 |
|---|---|---|
| committer | Tim Burke <tim.burke@gmail.com> | 2023-01-04 10:50:01 -0800 |
| commit | f77172e2ad6fef4b226637b8ae099a6faf810978 (patch) | |
| tree | 9e0e58dafb489f23e28d6305bcb5e2aa87f7b503 /.zuul.yaml | |
| parent | 2d7c1dc6dd8a672c1f89a46b2423898d33ff63d2 (diff) | |
| download | swift-f77172e2ad6fef4b226637b8ae099a6faf810978.tar.gz | |
CI: pin tox at the project level
No sooner do we fix the gate than tox has a new release that breaks
it again. Let's give them a bit to settle down; in the mean time, stick
with 3.x.
See https://github.com/tox-dev/tox/issues/2811
Also simplify our warning suppressions. The message filter is a regex,
so any prefix of the message will suffice. This allows us to also drop a
new message seen on CentOS 8:
CryptographyDeprecationWarning: Python 3.6 is no longer
supported by the Python core team. Therefore, support for
it is deprecated in cryptography. The next release of
cryptography (40.0) will be the last to support Python 3.6.
As we've previously seen with cryptography warnings, this can slow down
our probe tests to the point that they time out.
Change-Id: I316170442c67c1b4a5b87f9a1168cc04ca2417b8
Diffstat (limited to '.zuul.yaml')
| -rw-r--r-- | .zuul.yaml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/.zuul.yaml b/.zuul.yaml index 0491d92a3..60f7bf323 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -659,6 +659,8 @@ - swift-tox-func-py38-arm64 - project: + vars: + ensure_tox_version: '<4' templates: - publish-openstack-docs-pti - periodic-stable-jobs |