diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2021-11-26 18:43:23 -0500 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2021-11-26 18:49:34 -0500 |
commit | 9c5dfddfbd405a72d33b72ed097690a6c2c88b3a (patch) | |
tree | aea517f1a833ddd81b4ab5e2178d38f943773e3a /lib/sqlalchemy/testing/plugin/plugin_base.py | |
parent | 5eb407f84bdabdbcd68975dbf76dc4c0809d7373 (diff) | |
download | sqlalchemy-9c5dfddfbd405a72d33b72ed097690a6c2c88b3a.tar.gz |
"graceful fetch" test should....clean up gracefully!
this test was relying on gc to close out the connection.
this would lead to problems with aiosqlite as we invalidate
async connetions that aren't gracefully closed, and this test
suite was create tables per suite, so we'd get into a spot where
a new sqlite memory connection without the tables would get set up.
would only occur for full test run + -n2 + C extensions + python 3.7,
but we assume that is all related to just getting gc to trigger
or not trigger at exactly the right moment in this situation.
confirmed if we add a gc.collect() to the test without explcitly
closing out the conenction, the connection is gc'ed and detached,
and we get the error reproduced on the subsequent test.
Change-Id: Icc9d4bc703f0842c27600f532f34bc4c7d3baf21
Diffstat (limited to 'lib/sqlalchemy/testing/plugin/plugin_base.py')
0 files changed, 0 insertions, 0 deletions