#33213: Document coverage setup for parallel tests
-------------------------------------+-------------------------------------
Reporter: Mr. Glass | Owner: Paolo
| Melchiorre
Type: New feature | Status: closed
Component: Documentation | Version:
Severity: Normal | Resolution: fixed
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 GitHub <noreply@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"070cbac0dbf6a09b55aad322137ab168b75bf56b" 070cbac]:
{{{
#!CommitTicketReference repository=""
revision="070cbac0dbf6a09b55aad322137ab168b75bf56b"
Restored multiprocessing concurrency on coverage.py settings
* Revert "Reverted "Fixed #33213 -- Doc'd testing code coverage in
parallel and used it.""
This reverts commit 78da5ca0c1f2ab3201f8f6cd629e80d805ea023d.
* Restored coverage multiprocess concurrency with threads
Investigating https://github.com/nedbat/coveragepy/issues/1585 revealed
that thread tracing gets disabled when passing
`concurrency = multiprocessing`. Adding `thread` restores it, and
ensures that the `auser()` is reported as covered since the test suite
uses `AsyncToSync` to execute this middleware (which spawns threads).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33213#comment:15>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187c4502c47-01d177fa-f822-42a7-8f9b-fc014f92ffce-000000%40eu-central-1.amazonses.com.
