#35849: ParallelTestSuite reports error occurred in arbitrary test instead of
setUpClass
--------------------------------------+------------------------------------
Reporter: David Winiecki | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: dev
Severity: Normal | Resolution:
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 Natalia Bidart):
* cc: Adam Johnson, Jacob Walls (added)
* stage: Unreviewed => Accepted
* type: Bug => Cleanup/optimization
* version: 5.0 => dev
Comment:
Hello David, thank you for your detailed report. I have reproduced the
issue as you indicated.
I find the distinction between this being an issue or not somewhat
ambiguous. In my view, the first test run "is" the one that fails... but
what leads me to accept this ticket is the fact that the error reporting
differs depending on whether `parallel=1` is set or not.
I will include a few folks in the ticket to see what they recommend, I
took an initial look at your PR but I think we need more expert eyes on
it.
--
Ticket URL: <https://code.djangoproject.com/ticket/35849#comment:6>
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/01070192a0de30f3-50a51290-bf85-4ce6-89c9-f4291b0fd3d1-000000%40eu-central-1.amazonses.com.
