Browser tests: sqlite3.InterfaceError under the live server fails a test at random #1024

New issue

Closed

opened 2026-10-20 06:52:44 +00:00 by tiagoagueda · 0 comments

tiagoagueda commented

2026-10-20 06:52:44 +00:00

Owner

The browser job on the merge commit of #1015 (bd549fd81) failed on one test out of 865:

tests/e2e/test_application_filters.py::test_filters_the_page_came_with_can_be_changed_and_cleared_from_their_headers[chromium-scripts on]

The live server answered /applications/ with a 500 while loading the session, before any application code ran:

django.db.utils.InterfaceError: bad parameter or other API misuse (sqlite3.InterfaceError), raised from SessionStore.load() in django/contrib/sessions/backends/db.py.

That points to one SQLite connection used from two threads at once, the live-server thread and the test thread. #1015 does not touch the applications page, and the same job passed on the PR.

To do: find which fixture shares the connection (in-memory database, live_server, or a test thread querying while the server answers) and give the server its own, or serialise the two. Check whether other e2e tests could fail the same way.

The browser job on the merge commit of #1015 (`bd549fd81`) failed on one test out of 865: `tests/e2e/test_application_filters.py::test_filters_the_page_came_with_can_be_changed_and_cleared_from_their_headers[chromium-scripts on]` The live server answered `/applications/` with a 500 while loading the session, before any application code ran: `django.db.utils.InterfaceError: bad parameter or other API misuse` (`sqlite3.InterfaceError`), raised from `SessionStore.load()` in `django/contrib/sessions/backends/db.py`. That points to one SQLite connection used from two threads at once, the live-server thread and the test thread. #1015 does not touch the applications page, and the same job passed on the PR. To do: find which fixture shares the connection (in-memory database, `live_server`, or a test thread querying while the server answers) and give the server its own, or serialise the two. Check whether other e2e tests could fail the same way.

tiagoagueda added this to the 0.5.0 milestone

2026-10-25 17:04:12 +00:00

tiagoagueda referenced this issue from a pull request that will close it,

2026-10-28 14:37:43 +00:00

Keep the browser tests' database in a file, a connection per request (#1024) #1074

tiagoagueda referenced this issue from a commit

2026-10-28 14:37:44 +00:00

Keep the browser tests' database in a file, a connection per request (#1024)

tiagoagueda referenced this issue

2026-10-28 18:20:13 +00:00

Cache what every CI job rebuilt, and fetch no map tiles in tests (#1033) #1083

tiagoagueda referenced this issue from a commit