#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: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Simon Charette):
> Why is this a problem? When running multiple test suites at once, this
leads to filename collision if two test suites are using the same database
name(s). It is impossible to run two Django test suites in parallel from
the same directory without encountering this issue.
I don't think that's something Django's test machinery claims to supports
by the way, I can't think of multiple things that would break running
multiple test suites against the same checkout of a projects.
> Am I missing any step to trigger the parallel test DB creation?
You need to have at least two `TestCase` otherwise
[https://github.com/django/django/blob/6df19412aabb7d969f5eab4b2ff41269de89b233/django/test/runner.py#L989-L991
these is nothing to parallelize].
--
Ticket URL: <https://code.djangoproject.com/ticket/36496#comment:3>
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/01070197eb80f2de-c8435281-4771-4f27-b5b5-8a87d98db56f-000000%40eu-central-1.amazonses.com.
