]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Repair mssql dep tests; have __only_on__ imply __backend__
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 19 Dec 2020 15:59:42 +0000 (10:59 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 19 Dec 2020 17:36:57 +0000 (12:36 -0500)
commit31e7428b1622ce62a90d0270a2818dc785e210e9
tree24553562f4b304d1603241ef4ba2e91ee4d32707
parent27766512b2d037a8f0048dccc6e2f02c281fbc9a
Repair mssql dep tests; have __only_on__ imply __backend__

CI missed a few SQL Server tests because we run mssql-backendonly
in the gerrit job.   As there was a test that was "only on"
mssql but didn't have backendonly, it never got run and then
fails in master where we run mssql fully.

Any suite that has an __only_on__ is inherently specific to
a backend, so if present this should imply __backend__ so that
it definitely runs when we have that backend present.

This in turn meant we had to fix a few sqlite_file tests that
weren't cleaning up or sharing well as they suddenly became
backend tests under sqlite_file.  Added a sqlite_file cleanup
to test class cleanup for now.

Change-Id: I9de1ceabd6596547a65c59059a55b7e5156103fd
lib/sqlalchemy/dialects/sqlite/provision.py
lib/sqlalchemy/testing/plugin/plugin_base.py
test/dialect/mssql/test_deprecations.py
test/dialect/test_sqlite.py
test/requirements.py