Mike Bayer ca46caede4 adjustments for unreliable gc ...

sporadic (and at the moment persistent) test failures
related to aiosqlite seem to have in common that Python
gc stops working fully when we run a lot of tests with
aiosqlite.  The failures are not limited to aiosqlite
as they are more involving places where we assume or
expect gc.collect() to get rid of things, and it doesn't.

Identify (based on reproducible case on the d3 CI runner)
the spots where this happens and add fixes.

test/orm/test_transaction.py test_gced_delete_on_rollback
has always been a very sensitive test with a lot of issues,
so here we move it to the test_memusage suite and limit
it only to when the memusage suite is running.

Change-Id: I683412d0effe8732c45980b40722e5bb63431177

2022-12-04 23:31:20 -05:00

..

aaa_profiling

adjustments for unreliable gc

2022-12-04 23:31:20 -05:00

base

disallow same-named columns, unchecked replacement in Table

2022-12-04 10:45:35 -05:00

dialect

Merge "Fix positional compiling bugs" into main

2022-12-02 14:31:17 +00:00

engine

disallow same-named columns, unchecked replacement in Table

2022-12-04 10:45:35 -05:00

ext

Order_by and group_by accept labels

2022-12-03 13:04:58 -05:00

orm

adjustments for unreliable gc

2022-12-04 23:31:20 -05:00

perf

Try running pyupgrade on the code

2022-11-16 23:03:04 +01:00

sql

disallow same-named columns, unchecked replacement in Table

2022-12-04 10:45:35 -05:00

__init__.py

…

binary_data_one.dat

…

binary_data_two.dat

…

conftest.py

correct for pytest discovery

2022-03-04 16:28:31 -05:00

profiles.txt

perf improvements related to corresponding_column (2)

2022-11-15 14:16:06 -05:00

requirements.py

adjustments for unreliable gc

2022-12-04 23:31:20 -05:00