#32746: Unexpected test failures in 3.3.2 when running the whole testsuite
-----------------------------------+--------------------------------------
Reporter: Jakub Kulík | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | 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
-----------------------------------+--------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:4 Jakub Kulík]:
> Unfortunately, it seems so... Do you have any pointers/ideas on how I
should debug this? I'll try to find and fix the issue.
It would help to find test classes (or even a set of tests) that are
reproducing this issue without running the entire test suite. Maybe
`test_runner` is enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/32746#comment:5>
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/066.e40f5164062e38bc61a7aa5daec09629%40djangoproject.com.
