Skip to content

Fix grep regex for coverage parsing#20

Merged
leynos merged 2 commits intomainfrom
codex/troubleshoot-coverage-task-failure
Jul 5, 2025
Merged

Fix grep regex for coverage parsing#20
leynos merged 2 commits intomainfrom
codex/troubleshoot-coverage-task-failure

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 5, 2025

Summary

  • fix look-ahead usage in coverage parser

Testing

  • git status --short

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

Summary by Sourcery

CI:

  • Update coverage parser regex to capture the percent sign and strip it for accurate percentage output

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 5, 2025

Reviewer's Guide

Replaced the unsupported lookahead-based regex in the coverage parser with a simpler pattern that captures the percent sign and then strips it via tr, improving compatibility and maintainability of the GitHub Action.

File-Level Changes

Change Details Files
Simplify coverage percentage extraction regex and strip trailing percent sign
  • Replaced lookahead regex (?=%) with a pattern including %
  • Piped matched output to tr -d '%' to remove the percent sign
  • Retained head -n1 to select the first match
.github/actions/ratchet-coverage/action.yml

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 5, 2025

Summary by CodeRabbit

  • Chores
    • Updated the method for extracting and processing coverage percentage from test reports, ensuring more accurate handling of the coverage value.

Summary by CodeRabbit

  • Chores
    • Improved the extraction and formatting of coverage percentage values in the coverage reporting workflow.

Walkthrough

The script for extracting the coverage percentage in the ratchet-coverage GitHub Action was updated. The regex now captures the percentage value along with the percent sign, which is then removed using tr -d '%' before setting the output variable.

Changes

File(s) Change Summary
.github/actions/ratchet-coverage/action.yml Modified regex and string processing for extracting coverage percent

Possibly related PRs

  • Add ratchet coverage action #12: Introduced the original ratchet-coverage GitHub Action and its coverage parsing logic, which is directly modified in this PR.

Poem

A regex hop, a coverage drop,
Now with a sign, then snipped in line.
The action’s neat, the numbers sweet,
As percentages march, precise and fleet.
🐇✨

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in a Comment
  • Commit Unit Tests in branch codex/troubleshoot-coverage-task-failure

🪧 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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 7aeed4b and 34b450a.

📒 Files selected for processing (1)
  • .github/actions/ratchet-coverage/action.yml (1 hunks)

Comment thread .github/actions/ratchet-coverage/action.yml Outdated
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@leynos leynos merged commit debf7d6 into main Jul 5, 2025
1 check was pending
@leynos leynos deleted the codex/troubleshoot-coverage-task-failure branch July 5, 2025 16:30
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 34b450a and 36fa659.

📒 Files selected for processing (1)
  • .github/actions/ratchet-coverage/action.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}`: Each action...

.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}: Each action must have its own directory under .github/actions/, containing action.yml, README.md, src/, tests/, and CHANGELOG.md

📄 Source: CodeRabbit Inference Engine (AGENTS.md)

List of files the instruction was applied to:

  • .github/actions/ratchet-coverage/action.yml
`.github/actions/*/action.yml`: Fill in action.yml with every input and output; ...

.github/actions/*/action.yml: Fill in action.yml with every input and output; mark required ones clearly
For composite actions and path context, use "${{ github.action_path }}" when referencing sibling scripts for portability

📄 Source: CodeRabbit Inference Engine (AGENTS.md)

List of files the instruction was applied to:

  • .github/actions/ratchet-coverage/action.yml

Comment on lines +50 to 51
percent=$(echo "$output" | grep -oEm1 '[0-9]+(\.[0-9]+)?%' | tr -d '%')
echo "percent=$percent" >> "$GITHUB_OUTPUT"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Good optimisation, but first-match may grab the wrong percentage

Dropping the head hop with -m1 is neat; however, -m1 still returns the very first percentage in the output, which for multi-crate workspaces is usually a crate-level figure, not the overall “Summary” line. This can silently mis-report coverage.

Consider anchoring to the Summary: line (or taking the last match) instead:

-percent=$(echo "$output" | grep -oEm1 '[0-9]+(\.[0-9]+)?%' | tr -d '%')
+percent=$(echo "$output" \
+  | awk '/^Summary:/ { for (i=1;i<=NF;i++) if ($i ~ /%$/) { gsub("%","",$i); print $i; exit } }')

(or keep grep but pipe through tail -n1).

Worth a quick check if the action will run on projects with multiple crates.


🏁 Script executed:

#!/bin/bash
set -e
echo "Displaying lines 1-200 of action.yml for context:"
sed -n '1,200p' .github/actions/ratchet-coverage/action.yml || echo "File not found."

Length of output: 2718


🌐 Web query:

What does cargo llvm-cov --summary-only output look like for a multi-crate workspace?

💡 Result:

When you run cargo llvm-cov --summary-only in a multi-crate workspace, it generates a summary of code coverage for each crate in the workspace. The output typically includes the following information for each crate:

  • Crate Name: The name of the crate.
  • Total Lines: The total number of lines in the crate's source code.
  • Covered Lines: The number of lines that have been executed during testing.
  • Uncovered Lines: The number of lines that have not been executed during testing.
  • Coverage Percentage: The percentage of lines that have been covered by tests.

This summary helps you quickly assess the test coverage across all crates in your workspace.

For more detailed information on using cargo llvm-cov and its options, you can refer to the official documentation. (docs.rs)

Citations:


Anchor coverage extraction to the overall “Summary:” line

The current grep with -m1 will grab the first percentage in multi-crate output (a crate-level figure), not the final workspace summary. To ensure you report the true overall coverage, filter on the “Summary:” line or take the last match. For example, in .github/actions/ratchet-coverage/action.yml step Run coverage (around lines 50–51):

- percent=$(echo "$output" | grep -oEm1 '[0-9]+(\.[0-9]+)?%' | tr -d '%')
+ # Option 1: anchor to the "Summary:" line
+ percent=$(echo "$output" \
+   | grep '^Summary:' \
+   | grep -oE '[0-9]+(\.[0-9]+)?%' \
+   | tr -d '%')
  
  # Or Option 2: take the last match
# percent=$(echo "$output" \
#   | grep -oE '[0-9]+(\.[0-9]+)?%' \
#   | tail -n1 \
#   | tr -d '%')

Please update the extraction logic to avoid mis-reporting coverage in multi-crate workspaces.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
percent=$(echo "$output" | grep -oEm1 '[0-9]+(\.[0-9]+)?%' | tr -d '%')
echo "percent=$percent" >> "$GITHUB_OUTPUT"
# Option 1: anchor to the "Summary:" line
percent=$(echo "$output" \
| grep '^Summary:' \
| grep -oE '[0-9]+(\.[0-9]+)?%' \
| tr -d '%')
# Or Option 2: take the last match
# percent=$(echo "$output" \
# | grep -oE '[0-9]+(\.[0-9]+)?%' \
# | tail -n1 \
# | tr -d '%')
echo "percent=$percent" >> "$GITHUB_OUTPUT"
🤖 Prompt for AI Agents
In .github/actions/ratchet-coverage/action.yml around lines 50 to 51, the
coverage extraction uses grep with -m1 which captures the first percentage
found, often a crate-level coverage, not the overall summary. Modify the
extraction logic to first filter the output lines containing "Summary:" and then
extract the percentage from that line, or alternatively, capture the last
percentage match in the entire output. This ensures the reported coverage
reflects the true overall workspace summary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant