Repository navigation
ci: use LLVM instrumentation for coverage - #485
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #485 +/- ##
===========================================
+ Coverage 43.97% 85.10% +41.12%
===========================================
Files 85 96 +11
Lines 7281 9271 +1990
===========================================
+ Hits 3202 7890 +4688
+ Misses 4079 1381 -2698 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Mec-iS
approved these changes
Oct 12, 2026
3 tasks done
Mec-iS
added a commit
that referenced
this pull request
Oct 12, 2026
* chore: fold unreleased changes into the 0.6.16 release notes 0.6.16 has not been published to crates.io yet, so the [Unreleased] section is folded into the existing 0.6.16 entry instead of opening a new version. Covers #475, #478, #481, #482, #485. All release gates verified locally: - cargo test --all-features (614 unit + 73 doctests, 0 failed) - cargo fmt --all -- --check - cargo clippy --all-features (2018+2024 idioms, -Dwarnings) - cargo +1.85.0 build --all-features (MSRV) - cargo package (146 files, 2.1MiB) * ci: run coverage in release mode and shrink test_logit The LLVM coverage engine instruments the whole serial test run (--test-threads 1). On a slow shared runner the instrumented run could exceed tarpaulin's default 60 s per-binary timeout; observed as 'Timed out waiting for test response' while test_logit (a 52181x94 logistic-regression fit) was running. Two changes: - test_logit now uses a 10000x94 matrix with the same class ratio (418 of 10000 positive). The test asserts the same property and finishes in ~0.5 s instead of ~3.5 s. - The coverage job builds in release mode (--release) and raises the tarpaulin timeout to 600 s.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #484
Current behavior
The Linux coverage job uses Tarpaulin's default ptrace engine. With the optimized test profile, it can report executed source lines as uncovered. PR #480 exposed this in matrix products and estimator fits that the existing tests call.
New expected behavior
Install
llvm-tools-previewwith the nightly toolchain and run Tarpaulin with--engine llvm. LLVM instrumentation measures execution without relying on debug line mappings. The job still runs unit tests, integration tests, and doctests, produces LCOV output, and enforces the existing 44% threshold.Validation
cargo fmt --all -- --checkpassed.cargo clippy --all-features -- -Drust-2018-idioms -Drust-2024-compatibility -Dwarningspassed.Checklist
main.