ci: integrate Codecov test analytics via cargo-nextest#541
ci: integrate Codecov test analytics via cargo-nextest#541xdustinface wants to merge 2 commits intov0.42-devfrom
cargo-nextest#541Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v0.42-dev #541 +/- ##
=============================================
- Coverage 65.95% 65.95% -0.01%
=============================================
Files 311 311
Lines 64586 64586
=============================================
- Hits 42599 42597 -2
- Misses 21987 21989 +2
|
Switch CI test runner from `cargo test` to `cargo-nextest` to produce JUnit XML reports. Results are uploaded to Codecov's new test analytics feature for tracking test duration trends, failure rates, and flaky tests.
xdustinface
force-pushed
the
ci/codecov-test-analytics
branch
from
3e157f0 to
1596bff
Compare
- Serialize `dashd_sync` integration tests via nextest test-groups (nextest runs each test as a separate process concurrently, causing dashd resource contention and crashes) - Add `--no-tests=pass` to nextest commands so crates with zero tests (like `dash-fuzz`) don't fail - Output explicit JUnit file list instead of glob pattern to avoid Windows path expansion issues with codecov CLI
xdustinface
force-pushed
the
ci/codecov-test-analytics
branch
from
1596bff to
7cdd7e8
Compare
1 participant
Switch CI test runner from
cargo testtocargo-nextestto produce JUnit XML reports. Results are uploaded to Codecov's new test analytics feature for tracking test duration trends, failure rates, and flaky tests.