Coverage reports from the test suite exclude coverage provided by child processes #2978

Closed
opened 2019-02-26 18:23:11 +00:00 by exarkun · 2 comments

The test suite runs quite a few child processes. The way coverage is collected, any code that is run in these child processes does not count towards coverage in the report that is ultimately generated.

This makes some covered code appear uncovered. This makes the coverage reporting performed by CI less useful since reports of uncovered code must be manually investigated to determine if they are really uncovered or if they are covered in a child process.

The test suite runs quite a few child processes. The way coverage is collected, any code that is run in these child processes does not count towards coverage in the report that is ultimately generated. This makes some covered code appear uncovered. This makes the coverage reporting performed by CI less useful since reports of uncovered code must be manually investigated to determine if they are really uncovered or if they are covered in a child process.
exarkun added the
unknown
normal
defect
1.12.1
labels 2019-02-26 18:23:11 +00:00
exarkun added this to the undecided milestone 2019-02-26 18:23:11 +00:00
Author

(https://coverage.readthedocs.io/en/latest/subprocess.html) details the support built in to coverage.py for this kind of thing.

(https://coverage.readthedocs.io/en/latest/subprocess.html) details the support built in to coverage.py for this kind of thing.
Author
This is a duplicate of <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2297>
exarkun added the
duplicate
label 2020-08-26 18:38:15 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2978
No description provided.