Skip to content

fix: provide Rust LLVM coverage tools - #715

Closed
seonghobae wants to merge 2 commits into
mainfrom
fix/opencode-rust-coverage-llvm-tools
Closed

fix: provide Rust LLVM coverage tools#715
seonghobae wants to merge 2 commits into
mainfrom
fix/opencode-rust-coverage-llvm-tools

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

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:

  • workflow YAML parsed successfully
  • test harness syntax check passed
  • focused toolchain assertions passed
  • CodeGraph reindexed at the changed source
  • diff checks passed

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.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: de62e19a-7c4c-4f3c-9d2a-11a15bd90a3a

📥 Commits

Reviewing files that changed from the base of the PR and between db70439 and 6a48d12.

📒 Files selected for processing (2)
  • .github/workflows/opencode-review-dispatch.yml
  • scripts/ci/test_strix_quick_gate.sh

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Contributor Author

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.

@seonghobae seonghobae closed this Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant