diff options
author | Stephen Finucane <stephenfin@redhat.com> | 2021-08-16 12:35:27 +0100 |
---|---|---|
committer | Stephen Finucane <stephenfin@redhat.com> | 2021-11-12 09:43:38 +0000 |
commit | 52bd1e51d675a1eb1226a45e3e952b17bda712a2 (patch) | |
tree | 5d6a90fd0f5d7ed6cc6e579826e293bc90b0d4cd /tox.ini | |
parent | e28afc564700a1a35e3bf0269687d5734251b88a (diff) | |
download | nova-52bd1e51d675a1eb1226a45e3e952b17bda712a2.tar.gz |
tests: Enable SQLAlchemy 2.0 deprecation warnings
Well, sort of. We enable them but immediately filter out the ones we're
actually seeing, the rationale being that we can address these in a
piecemeal fashion without the risk of introducing new issues.
There's a lot more to be done here. However, the work done in oslo.db
[1] should provide a guide for how to resolve the outstanding issues.
[1] https://review.opendev.org/q/topic:%2522sqlalchemy-20%2522+project:openstack/oslo.db
Change-Id: Iafe726d3819031c357460fd131bb2bb58babb4e2
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Diffstat (limited to 'tox.ini')
-rw-r--r-- | tox.ini | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -23,6 +23,8 @@ setenv = OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=160 PYTHONDONTWRITEBYTECODE=1 +# TODO(stephenfin): Remove once we bump our upper-constraint to SQLAlchemy 2.0 + SQLALCHEMY_WARN_20=1 deps = -c{env:TOX_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt |