#29023: running tests in parallel doesn't show exception chain, even with tblib
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
parallel,exception,chain,traceback,pickling,tblib|
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
For future reference, here is one possible work-around that I think would
be better than the status quo. If an exception raised during a test either
(1) fails the "pickleable test," or (2) has a chain of length bigger than
one (e.g. non-`None` `__cause__` attribute), then the traceback could be
formatted to a string in the child process and a pickleable exception of
the form `UnpickleableTestException(traceback)` could be sent back to the
parent process. The end result won't look as clean as the pickled case,
but at least the information of the full exception chain should display.
Also, in the case of unpickleable exceptions, it should prevent the test
run from aborting completely. So it would address two issues.
--
Ticket URL: <https://code.djangoproject.com/ticket/29023#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 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/067.4fcdf7ebf8419bd801756a70658f125e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
