#14296: 'manage.py test' failing for apps that access read-only databases
-----------------------------------+-------------------------------------
Reporter: kthhrv | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 1.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+-------------------------------------
Changes (by Jacob Walls):
* status: new => closed
* resolution: => needsinfo
Comment:
It's likely that the use case from comment:14 is solved through the
combination of setting `'TEST': {'MIGRATE': False}` (new in 3.1) and the
fix for #23273 (merged for 4.1) to skip creating the `django_migrations`
table.
Setting back to `needsinfo` in case someone has details to add around the
interaction of read-only databases with the test runner.
--
Ticket URL: <https://code.djangoproject.com/ticket/14296#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/064.b108821679e6902ae9bdbd2d17dc5e35%40djangoproject.com.
