#29062: "database table locked errors" when using sqlite in-memory database with
LiveServerTestCase
-------------------------------------+-------------------------------------
Reporter: Juozas Masiulis | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 2.0
Severity: Normal | Resolution:
| worksforme
Keywords: sqlite, testing, | Triage Stage:
databases | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => worksforme
Comment:
Is the error consistent? I ran your sample project ten times and the test
usually passes. Once in a while, I see this failure:
{{{
======================================================================
FAIL: testStuff (bugdemo.tests.TestDatabaseLocking)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/tim/code/django-bug-demo/bugdemo/tests.py", line 75, in
testStuff
self.assertEqual(Question.objects.count(), 30)
AssertionError: 29 != 30
}}}
I think you'll have to explain why Django is at fault to move this report
forward. Possibly the problem might be dependent on the Python version. I
tested with Python 3.4.7, 3.5.5, and 3.6.4.
--
Ticket URL: <https://code.djangoproject.com/ticket/29062#comment:5>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.42ed3c782aa2473ed1f4eb04066f5bab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
