At least report the coverage on the command line

[jan-janssen]

Summary by CodeRabbit

• Chores
  • Added a step to display a coverage summary in the console during continuous integration runs.

[coderabbitai]

Walkthrough

A command was added to the CI workflow to output a coverage summary to the console during the unittest_flux_openmpi job. This occurs after running coverage-based tests and before generating the coverage XML file. No other logic or control flow changes were introduced.

Changes

File(s)	Change Summary
.github/workflows/pipeline.yml	Added coverage report; command to output coverage summary

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped through CI night,
And saw the coverage shining bright.
With one small line, the stats appeared,
Console reports—just as we cheered!
Now every build, with coverage shown,
The rabbit smiles, no stats unknown.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch coverage_report

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ad2b493 and 06a9e6b.

📒 Files selected for processing (1)

• .github/workflows/pipeline.yml (1 hunks)

[coderabbitai]

🛠️ Refactor suggestion

⚠️ Potential issue

Use && instead of ; to avoid masking test failures

The current chaining

flux start
coverage run -a … -m unittest …; coverage report; coverage xml

means the job’s exit status is that of coverage xml, not the unit-test invocation.
If any test fails, coverage run exits non-zero, but the subsequent commands still run and return 0, so the CI job can appear green while tests are red.

-flux start
-coverage run -a --omit="executorlib/_version.py,tests/*" -m unittest tests/test_fluxpythonspawner.py tests/test_fluxjobexecutor_plot.py tests/test_fluxjobexecutor.py tests/test_fluxclusterexecutor.py; coverage report; coverage xml
+flux start \
+coverage run -a --omit="executorlib/_version.py,tests/*" -m unittest \
+  tests/test_fluxpythonspawner.py \
+  tests/test_fluxjobexecutor_plot.py \
+  tests/test_fluxjobexecutor.py \
+  tests/test_fluxclusterexecutor.py && \
+coverage report && \
+coverage xml

Using && (or set -e) ensures the step fails immediately on the first non-zero exit code, preserving proper CI signalling.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In .github/workflows/pipeline.yml around lines 256 to 260, the commands chaining
test execution and coverage reporting use semicolons, which causes the step to
report success even if tests fail. Replace the semicolons with `&&` between the
commands so that each command only runs if the previous one succeeded, ensuring
the CI job fails immediately on test failures.