#33356: "python manage.py test" fails, but running the individual TestCase pass
-------------------------------+--------------------------------------
Reporter: Dylan Yung | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
It's not clear to me that Django is at fault. The accepted answer on
Stackoverflow says, "There's some weird internal bug where if you operate
on one table a lot with a lot of different TestCase classes then it'll do
a DB check at the end after it's been torn down and it'll cause an error."
but it's not clear that this is just speculation.
You need to at least provide a far simpler minimal example to reproduce
the problem, and ideally, explain why Django is at fault. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/33356#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 on the web visit
https://groups.google.com/d/msgid/django-updates/069.faa0bfc4494e841bd11f60e73aefcde5%40djangoproject.com.