#29062: "database table locked errors" when using sqlite in-memory database with
LiveServerTestCase
-------------------------------------+-------------------------------------
Reporter: Juozas Masiulis | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 2.0
Severity: Normal | Resolution:
Keywords: sqlite, testing, | Triage Stage: Accepted
databases |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Spencer):
Replying to [comment:12 Andrew Badr]:
> Yep, I'm hitting this too. See workaround at
https://stackoverflow.com/questions/48353002/sqlite-database-table-is-
locked-on-tests
This workaround does not work for me. I'm using the LiveServerTestCase to
run a series of Selenium tests checking Ajax functionality, so the result
of switching the LiveServerThread back to single-threaded WSGIServer only
replaces the deadlock error with a timeout error. The Ajax calls timeout
waiting for the main server thread to exit, which it never does.
--
Ticket URL: <https://code.djangoproject.com/ticket/29062#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.f87e8fbc215a1ede0516b6d446f38660%40djangoproject.com.
