Commit d6152af1 authored by Kevin Modzelewski's avatar Kevin Modzelewski

I think we just have to skip this test

After much investigation, I think this is the best option for now.
We might need to patch sqlalchemy or switch to refcounting.

The issue is that there's a dangling cursor that's left open, and
under cpython it will get closed quickly.  But for us, it's left open,
which keeps the connection open.  This leaves the table its referencing
locked.  But only in old versions of sqlite!  Newer versions are smart
enough to know that 'select current_timestamp() from table' does not
need to lock the table, so even though that select statement is still
running, it doesn't end up locking the table.

PyPy has a different issue with the test, where it closes the cursor too
early (not sure why).
parent 7d34094c
...@@ -207,6 +207,11 @@ for run_idx in xrange(1): ...@@ -207,6 +207,11 @@ for run_idx in xrange(1):
if clsname == "SelectTest" and t == 'test_binds': if clsname == "SelectTest" and t == 'test_binds':
continue continue
# This test relies on quick destruction of cursor objects,
# since it's not getting freed explicitly.
if 'test_bind' in mname and t == 'test_clauseelement':
continue
print "Running", t print "Running", t
try: try:
try: try:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment