Check llvm-tools-preview component for coverage

[leynos]

Summary

• verify rustup llvm-tools-preview component before coverage run

Testing

• make fmt
• make lint
• make test

---

https://chatgpt.com/codex/tasks/task_e_689cd9a6cd388322b071444114a09b8d

Summary by Sourcery

Enhancements:

• Extend the coverage target to verify that the llvm-tools-preview component is installed via rustup

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The Makefile’s coverage validation target is enhanced to also verify that the rustup llvm-tools-preview component is installed before running cargo-llvm-cov.

Flow diagram for updated coverage check in Makefile

flowchart TD
    A[Start coverage check] --> B{Is cargo-llvm-cov installed?}
    B -- No --> C[Show error: Install cargo-llvm-cov]
    B -- Yes --> D{Is llvm-tools-preview component installed?}
    D -- No --> E[Show error: Install llvm-tools-preview]
    D -- Yes --> F[Proceed with coverage run]

Loading

File-Level Changes

Change	Details	Files
Extend coverage pre-check to require rustup llvm-tools-preview component	Run “rustup component list --installed” and grep for llvm-tools-preview Emit an error and exit with install instructions if the component is missing	Makefile

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 47 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 9ce5f9b and 847a986.

📒 Files selected for processing (1)

• Makefile (1 hunks)

Summary by CodeRabbit

• Chores
  • Improved build-time validation for developer environments by checking required LLVM tooling and providing clearer error messages with installation guidance when missing.
  • Minor formatting clean-up in build configuration; no impact on features, behaviour, or performance.

Walkthrough

Add a rustup llvm-tools-preview component check to the Makefile’s CHECK_CARGO_LLVM_COV macro alongside the existing cargo-llvm-cov check. Emit a specific error and exit 127 when missing. Reformat indentation within the macro without changing behaviour.

Changes

Cohort / File(s)	Summary of changes
Makefile coverage checks Makefile	Update CHECK_CARGO_LLVM_COV to require rustup llvm-tools-preview component; keep cargo-llvm-cov check; print install hint on failure; exit 127; reformat indentation (tabs → spaces).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Switch coverage to llvm-cov lille#106 — Align coverage setup with cargo-llvm-cov; both touch coverage tooling prerequisites.
• Add coverage test target #58 — Extend Makefile coverage targets relying on cargo-llvm-cov; shares the same prerequisite checks.

Poem

Tighten the gears of the build machine,
Demand the tools, keep pathways clean.
llvm’s keys now guard the gate,
Fail with a hint, don’t hesitate.
Tabs to spaces, lines align—
Coverage awakens, crisp and fine. 🛠️📊

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/add-pre-flight-check-for-llvm-tools-preview

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[leynos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[leynos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[leynos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[leynos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4df0b66 and 9ce5f9b.

📒 Files selected for processing (1)

• Makefile (1 hunks)

🔇 Additional comments (1)

Makefile (1)

12-19: Fail fast on missing coverage dependencies. LGTM.

The pre-flight checks improve developer UX by surfacing actionable errors before running coverage jobs.

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}