Skip to content

CI: support parallel coverage in reusable python workflow#240

Open
pdelsante wants to merge 1 commit into
developfrom
ci/parallel-coverage-combine
Open

CI: support parallel coverage in reusable python workflow#240
pdelsante wants to merge 1 commit into
developfrom
ci/parallel-coverage-combine

Conversation

@pdelsante

Copy link
Copy Markdown
Member

Allow projects to run the Django test suite in parallel under coverage:

  • drop -a from coverage run (append is incompatible with coverage parallel mode, concurrency=multiprocessing / parallel=true);
  • add a guarded coverage combine step before the coverage report so the per-process .coverage.* files produced by parallel workers are merged.

Both changes are no-ops for projects that don't use parallel coverage (single coverage run needs no append; combine is skipped when there are no .coverage.* files). Applied to workflows/_python.yml and its hard-linked .github/ self-test copy.

Allow projects to run the Django test suite in parallel under coverage:
- drop `-a` from `coverage run` (append is incompatible with coverage
  parallel mode, concurrency=multiprocessing / parallel=true);
- add a guarded `coverage combine` step before the coverage report so the
  per-process .coverage.* files produced by parallel workers are merged.

Both changes are no-ops for projects that don't use parallel coverage
(single coverage run needs no append; combine is skipped when there are no
.coverage.* files). Applied to workflows/_python.yml and its hard-linked
.github/ self-test copy.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants