#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 Damian Posener):
Replying to [comment:2 abhishek1999]:
> Hi π β Iβm trying to reproduce this bug to help confirm .
>
> Hereβs what I did so far:
>
> 1. Created a test project with the `DATABASES` config exactly as
described.
> 2. Ran `migrate` β the `.sqlite3` file was created correctly in
`db/default/`.
> 3. Added a simple `TestCase` with multiple dummy tests.
> 4. Ran `python manage.py test --keepdb --parallel=auto`.
>
> **Environment:**
> - Django version: `6.0.dev20250612075530` (editable install)
> - Python version: `3.12.11`
> - SQLite version: `3.43.2`
>
> I only see `db/default/db.sqlite3` β no additional `default_1.sqlite3`
or `other_1.sqlite3` files appear in the project root.
>
> Am I missing any step to trigger the parallel test DB creation?
> Any suggestions are appreciated β thanks!
There is a demo project attached to this ticket as a zip file. If you
extract that and run tests you can replicate the issue hopefully.
--
Ticket URL: <https://code.djangoproject.com/ticket/36496#comment:4>
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/01070197ee4c267f-e902a171-6e13-422f-ba72-820abe6c6e7b-000000%40eu-central-1.amazonses.com.
