ci(codecov): collect and upload coverage from cpu-tests#298
Conversation
Adds coverage collection to the cpu-tests task (--cov=sampleworks --cov-report=xml, pytest-cov is already a dev/test dependency) and a Codecov upload step to the cpu-tests CI job, flagged per model environment (boltz-dev/protenix-dev/rf3-dev). Adds codecov.yml with auto targets and per-flag carryforward. The upload uses fail_ci_if_error: false so CI stays green until the Codecov app and CODECOV_TOKEN secret are configured on the repo. Fixes diff-use#126.
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR wires Codecov into the existing CI pipeline by generating a coverage.xml report during the cpu-tests matrix job (per model environment) and uploading that report to Codecov with per-environment flags, plus a repository-level codecov.yml to control status targets and PR comments. Confidence: ~85% (I’m confident the wiring is correct; Codecov’s exact token/permission nuances can vary over time and repo settings).
Changes:
- Add coverage collection to the
cpu-testspixi task viapytest-cov(--cov=sampleworks --cov-report=xml --cov-report=term). - Upload
coverage.xmlfrom thecpu-testsCI job usingcodecov/codecov-action@v4, flagged bymatrix.environment. - Introduce
codecov.ymlto enable auto targets for project/patch, carryforward flags, and PR diff comments.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
pyproject.toml |
Extends the cpu-tests task to emit coverage.xml for CI collection. |
codecov.yml |
Adds Codecov status/comment/flag management settings aligned with per-env uploads. |
.github/workflows/ci.yml |
Uploads the generated coverage.xml to Codecov per environment flag. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Fixes #126.
Wires up Codecov:
cpu-testsnow runspytest ... --cov=sampleworks --cov-report=xml --cov-report=term(pytest-covis already a dev/test dependency, so no new deps).codecov/codecov-action@v4step to thecpu-testsjob, flagged per model environment (boltz-dev/protenix-dev/rf3-dev) so per-env coverage is visible and merged for the overall number.codecov.yml—autoproject/patch targets with a 1% threshold, per-flag carryforward, and diff comments on PRs.One maintainer step needed to activate
The upload uses
fail_ci_if_error: false, so CI stays green regardless. To turn Codecov on:diff-use/sampleworks.CODECOV_TOKENactions secret.(Public repos can upload tokenless, but setting the token is the reliable path and required if the repo is private.)
Closes #126.