Add code coverage reporting to PR CI #6518
Draft
+69
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Copilot
AI
changed the title
[WIP] Add code coverage report to CI
Add code coverage reporting to PR CI
Dec 25, 2025
youknowone
force-pushed
the
copilot/add-code-coverage-report
branch
4 times, most recently
from
c2b5586 to
b7a0001
Compare
youknowone
force-pushed
the
copilot/add-code-coverage-report
branch
from
b7a0001 to
76ad42c
Compare
Co-authored-by: youknowone <[email protected]>
youknowone
force-pushed
the
copilot/add-code-coverage-report
branch
from
76ad42c to
6817d2a
Compare
- Use `cargo llvm-cov build` instead of `cargo build` to ensure proper coverage instrumentation - Add `--target-dir target` to keep binaries in standard location - Add `--no-report` since report is generated separately - Update clean and report commands to use same target-dir Co-Authored-By: Claude Opus 4.5 <[email protected]>
Co-Authored-By: Claude Opus 4.5 <[email protected]>
cargo llvm-cov doesn't have a build subcommand. Use environment variables from show-env with regular cargo build. Co-Authored-By: Claude Opus 4.5 <[email protected]>
Use heredoc format for RUSTFLAGS which contains spaces. GitHub Actions requires this format for multiline/space-containing values: NAME<<EOF value EOF Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Add Trim() to handle Windows line endings - Change regex to not require end-of-line match - Add debug output to verify env vars are being set Co-Authored-By: Claude Opus 4.5 <[email protected]>
Without --export-prefix, output is "RUSTFLAGS='...'" not "export RUSTFLAGS='...'" so the regex didn't match. Co-Authored-By: Claude Opus 4.5 <[email protected]>
- source <() (process substitution) not supported in sh - Use eval "$(...)" which is POSIX compliant - Add explicit shell: bash Co-Authored-By: Claude Opus 4.5 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds code coverage collection to PR CI workflow using stable Rust's source-based coverage (available since 1.60.0). Coverage reports are uploaded to Codecov on every PR.
Implementation
codecovjob in.github/workflows/ci.yamlruns Rust test coverage onlycargo-llvm-covwith stable toolchain and rust-cachefail_ci_if_error: falseto avoid blocking PRs on Codecov service issuesskip:cilabelDesign
The PR job collects only Rust test coverage to minimize build time impact. The existing scheduled cron job continues to provide comprehensive coverage including Python snippets and full test suite.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.