#36496: SQLite test database path not recognised when running tests in parallel
-----------------------------------+------------------------------------
Reporter: Damian Posener | Owner: (none)
Type: Bug | Status: new
Component: Testing framework | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by Damian Posener):
Replying to [comment:10 Simon Charette]:
> Damian, do you have a requirement that parallel test databases are
backed by actual files instead of being in memory per worker process which
should ensure isolation?
>
> What I mean is that if you want to avoid collisions until this gets
fixed you could simply set `DATABASES['<alias>']['TEST']['NAME'] =
':memory:'` which is a common setup to speed up tests and ensure
isolation.
That would rather defeat the point of using `--keepdb`, don't you think?
:D We do run with in-memory DBs for a few applications, but that's an
inefficient choice when testing apps that have a load of migrations in
them.
--
Ticket URL: <https://code.djangoproject.com/ticket/36496#comment:11>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070197f367350d-d17d4501-7c09-4216-b8f5-cb3bcadb635e-000000%40eu-central-1.amazonses.com.
