#28320: Parallel testing: Please implement a signal or call checks after test DB
creation but before cloning it.
-------------------------------------+-------------------------------------
Reporter: László Károlyi | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Testing framework | Version: 1.11
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 László Károlyi):
Update:
It seems I managed to consistently insert the needed data into the DB
before it gets cloned by subclassing the testrunner and running checks
before `setup_databases()` runs. But that brought another problem I
discovered, and which maybe could be fixed.
So the first part I'm doing at startup is, I update my own permission
models, which subclass the original django `Permission` model. Formerly, I
had a function that would give a `ContentType` model of
`django.contrib.auth`:
{{{#!python
def _get_perm_contenttype(app_label: str, model_name: str):
"""
Return a `ContentType`.
"""
from django.contrib.contenttypes.models import ContentType
return ContentType.objects.get_for_model(
apps.get_model(app_label=app_label, model_name=model_name))
}}}
Because `ContentType.objects.get_for_model()` caches, and because the
nature of the parallel testing, that cached result sometimes brought
models with wrong `ID`s, and I got constraint violations because no such
IDs existed in my DB.
I fixed my code by not using `get_for_model()`, and using `get()` instead.
I'm just leaving this information here for your consideration.
--
Ticket URL: <https://code.djangoproject.com/ticket/28320#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.3f631739ad79b81ae61f4eea61e1b96a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
