Skip to content

ci: Use a separate benchmark filter - #7919

Open
mathbunnyru wants to merge 3 commits into
XRPLF:developfrom
mathbunnyru:no_bench_debug
Open

ci: Use a separate benchmark filter#7919
mathbunnyru wants to merge 3 commits into
XRPLF:developfrom
mathbunnyru:no_bench_debug

Conversation

@mathbunnyru

Copy link
Copy Markdown
Contributor

High Level Overview of Change

Doesn't make sense running benchmarks in debug builds

Context of Change

API Impact

  • Public API: New feature (new methods and/or new fields)
  • Public API: Breaking change (in general, breaking changes should only impact the next api_version)
  • libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
  • Peer protocol change (must be backward compatible or bump the peer protocol version)

@mathbunnyru
mathbunnyru requested a review from a team as a code owner July 30, 2026 19:23
@mathbunnyru mathbunnyru added Ready to merge *PR author* thinks it's ready to merge. Has passed code review. Perf sign-off may still be required. Trivial Simple change with minimal effect, or already tested. Only needs one approval. labels Jul 30, 2026
@codecov

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

# `install` target does not build them.
- name: Run the benchmarks
if: ${{ !inputs.build_only && runner.os != 'Windows' && env.SANITIZERS_ENABLED == 'false' && env.COVERAGE_ENABLED != 'true' && env.VOIDSTAR_ENABLED != 'true' }}
if: ${{ !inputs.build_only && runner.os != 'Windows' && inputs.build_type != 'Debug' && env.SANITIZERS_ENABLED == 'false' && env.COVERAGE_ENABLED != 'true' && env.VOIDSTAR_ENABLED != 'true' }}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

  • How about adding a new entry to the strategy matrix, benchmark, that defaults to false, and is only set to true in the specific configs you want them to run?
  • Alternatively, only run the benchmark for configs for which a package is built?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added a separate benchmark, thanks for suggestion!

Copilot AI left a comment

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.

Pull request overview

This PR updates the reusable CI build/test workflow so benchmark smoke-runs are skipped for Debug builds, aligning benchmark execution with its intent as a lightweight correctness check (not a performance run) and avoiding the extra runtime cost of Debug artifacts.

Changes:

  • Skip the “Run the benchmarks” step when inputs.build_type is Debug.
  • Update the surrounding workflow comments to document the additional skip condition.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mathbunnyru mathbunnyru changed the title ci: Don't run benchmark in Debug builds ci: Use a separate benchmark filter Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Ready to merge *PR author* thinks it's ready to merge. Has passed code review. Perf sign-off may still be required. Trivial Simple change with minimal effect, or already tested. Only needs one approval.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants