chore(ci): report-only coverage job for sentrix-core (non-blocking)#778
Conversation
sentrix-core is excluded from the required `cargo-llvm-cov` job because llvm-cov instrumentation of the revm dep tree is brittle on CI runners. Add a standalone, non-blocking job so we still get a sentrix-core coverage number without any risk to the required gate or to Codecov. - separate workflow; job name is NOT in the branch ruleset's required status checks, so it can never block a merge - continue-on-error: true → flaky/failed instrumentation is a soft failure - no codecov/codecov-action step → cannot change Codecov project/patch - publishes lcov + text summary as a downloadable CI artifact only - triggers only on PRs touching crates/sentrix-core/** + manual dispatch Does not modify coverage.yml or codecov.yml. Promote sentrix-core into the main coverage upload only once revm instrumentation is reliable on CI.
|
Warning Review limit reached
More reviews will be available in 19 minutes and 33 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
1 participant
Follow-up to #777. Adds a sentrix-core coverage number without any risk to the required gate or to Codecov.
Why
sentrix-coreis excluded from the requiredcargo-llvm-covjob (coverage.yml) because llvm-cov instrumentation of the revm dep tree is brittle on CI runners. So the new apply-path / fingerprint / native-module logic from #775/#776 has no coverage number in CI.What
A standalone
coverage-sentrix-core.yml:Test,cargo audit,gitleaks,cargo-llvm-cov,Dependency review,commitlint), so it can never block a merge.continue-on-error: true— if revm instrumentation flakes on the runner, it's a soft failure, not a red gate.codecov/codecov-actionstep, so it cannot move project/patch coverage.sentrix-core-lcov.info+ a text summary as a downloadable CI artifact.crates/sentrix-core/**+workflow_dispatch.Does not modify
coverage.ymlorcodecov.yml.Local verification
cargo test -p sentrix-core✅ (clean, ~37s, no flakiness)cargo llvm-cov -p sentrix-core --summary-only✅ ~49s warm → 82.5% regions / 77.9% lines (incl. the new vm.rs 86.7%, nft.rs apply path)Risk
Low. Worst case = the report-only job is slow or flakes on CI; because it's non-required + continue-on-error + artifact-only, that has zero impact on merges or the codecov number. Promoting sentrix-core into the required coverage upload stays deferred until revm instrumentation is proven reliable on CI.
No protocol logic, RPC, explorer, wallet, marketplace, or bridge changes. No deploy.