#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 Adam Wróbel):
Replying to [comment:4 Chris Jerdonek]:
> In the PR, you say--
>
> > One example of error like that is botocore.exceptions.ClientError
which pickles as "ClientError(message)", but its initializer is actually
ClientError(response, operation_name).
>
> In addition to creating this ticket, have you also tried reporting this
to the botocore project?
I've started writing a PR for botocore, but consider it a lower priority:
we can try to fix thousands of unpickleable errors, but with a robust test
runner it might not matter at all.
> > This ticket has two parts:
>
> This sounds like it should be taken care of by two separate PR's (and
indeed you created one PR to solve the first part). Does this mean you
should have two separate tickets? This way the two issues can be discussed
in isolation without confusing the two.
Indeed I could try to write a second PR if the second part of this ticket
was accepted.
As for two tickets, I was really hoping to have that minor adjustment from
first PR merged without any ticket at all. That one-direction-only check
seems like a trivial omission. I think @aaugustin would agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/27301#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/061.20866f18e06bbbcc8e270b6f09d5c889%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
