Test our microbenchmarks as part of CI

Open Beginner friendly
#24,868 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
ci-cd, testing

Research direction

Run cargo test --benches locally to confirm the intended check, then inspect the repository's existing CI workflows to find the appropriate job. Done means CI executes the microbenchmarks in debug, single-iteration test mode and fails when benchmark code panics; issue #15511 provides related context.

Written by the indexing model from the issue text.

Description

development-process enhancement
Is your feature request related to a problem or challenge?

We can test our benchmarks with cargo test --benches which runs in debug & single iteration, just to ensure the benchmark code actually executes. Have seen instances in arrow-rs where some were panicking but we didn't know since we didn't often run those benchmarks

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context
Dominant language
Rust
Stars
9.3k
Forks
2.4k
Avg merge
3d 8h
Merged PRs (30d)
354

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/datafusion

All issues in apache/datafusion

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.