#27301: Better handling of errors that are not pickleable when testing in
parallel
-------------------------------------+-------------------------------------
Reporter: Adam Wróbel | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution:
Keywords: testrunner parallel | Triage Stage: Accepted
pickle |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
> I've started writing a PR for botocore, but consider it a lower
priority:
Can you post a link to the issue?
> we can try to fix thousands of unpickleable errors, but with a robust
test runner it might not matter at all.
Thousands seems like an exaggeration to me. A dozen seems like a more
reasonable upper bound.
In any case, if a particular exception isn't picklable, it seems like that
should be reported as a bug each time we notice it -- regardless of the
state of Django's test runner, and regardless of the number of instances
we notice. Also, as long as Django relies on the picklability of
exceptions for the nicest form of error messages, it seems we should want
those exceptions to be picklable.
--
Ticket URL: <https://code.djangoproject.com/ticket/27301#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 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/061.7a79547b77ce2934f442a093b141ae1b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
