#25674: regression in test discovery
-----------------------------------+--------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.8
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 brian):
Having problems doing a reliable bisect.
bbe7964185fb786599b9f4bcaa07fc54156c9e0d - migrations don't seem to work
properly, get "django.db.utils.OperationalError: no such table:
auth_email" - this appears to happen before test discover although I am
not 100% certain on this.
next commit:
e55d888b6680a45ca957434599c37f0286034cab - no errors, no tests being run.
So it is possible that I found the commit that causes the problem. Or I
found the commit that fixes the db migration issue - which I don't
particularly care about. In actual fact I don't see anything in that
commit at quick glance should do any of the above.
Is there some work around for the no such table error so I can get a more
reliable bisect?
--
Ticket URL: <https://code.djangoproject.com/ticket/25674#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.8f2832b29a080974fc001dd09aa22720%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
