fix: provide Rust LLVM coverage tools - #715
Conversation
|
Warning Review limit reached
Next review available in: 37 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Comment |
|
Closing as superseded by #650's complete Rust coverage path. #715 only adds Debian LLVM binaries for the distribution toolchain; it does not address the same incident's modern Cargo.lock parsing or network-isolated crate availability. #650 covers the pinned modern Rust toolchain, llvm-tools, offline crate prefetch/cache, and deterministic offline selection. After #674 lands, #650 should be rebased and its overlapping Python base-lock portion reevaluated before merge. |
Fixes central coverage-evidence failures for system Rust toolchains by installing Debian rust-llvm, resolving llvm-cov and llvm-profdata from the active rustc sysroot, and exporting their trusted paths for cargo-llvm-cov.
Local validation:
The full quick-gate harness did not complete locally and exposed pre-existing pull-request context fixture failures unrelated to these two changed hunks. The PR CI image build is the authoritative runtime validation.