#32140: `startTest` result hook not called until after tests already started
when
`--parallel` used
-------------------------------------+-------------------------------------
Reporter: Bob Whitelock | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 3.1
Severity: Normal | Resolution: needsinfo
Keywords: startTest parallel | Triage Stage:
test runner | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Bob Whitelock):
> The reason this happens is that custom result classes aren't used in the
parallel processes, but instead RemoteTestResult, which mostly holds onto
the result to send it back to the main process for display. In theory it's
possible to change how that works, and might even allow the --debug-sql
and --pdb options work with --parallel, but it might require a little
thought.
Thanks for the explanation, and that's interesting - the custom startTest
method does appear to be called however, just after the test has actually
started, so it does look like the custom result class is being used.
Unless I'm misunderstanding what you mean?
--
Ticket URL: <https://code.djangoproject.com/ticket/32140#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/070.44e1815797c96110a1848deea9055940%40djangoproject.com.
