Skip to content

Narrow clippy expectations in tests - #72

Merged
SBALAVIGNESH123 merged 1 commit into
masterfrom
agent/narrow-clippy-expect-scopes
Jul 11, 2026
Merged

Narrow clippy expectations in tests#72
SBALAVIGNESH123 merged 1 commit into
masterfrom
agent/narrow-clippy-expect-scopes

Conversation

@SBALAVIGNESH123

Copy link
Copy Markdown
Owner

Summary

Follow-up to #71 CodeRabbit review.

This PR removes blanket file-level clippy expectations from engine tests and benchmark targets, then fixes the exposed lint debt directly where practical.

What changed

  • Removed all #![expect(...)] file-level clippy expectations from crates/omnikv-engine/tests and crates/omnikv-engine/benches.
  • Replaced broad suppressions with real cleanup for old format strings, doc-markdown findings, duplicate match arms, redundant clones, config initialization, unnecessary collects, and lock-scope tightening.
  • Kept only narrow item/helper-level expectations where they are intentional:
    • benchmark throughput helper casts
    • benchmark soak harness length
    • two long Raft end-to-end scenario tests
  • Preserved behavior while making future lint regressions visible to CI.

Why

CodeRabbit correctly pointed out that file-level #[expect] attributes can hide future lint debt in the same test target. This follow-up scopes the remaining exceptions to the smallest useful item and removes many exceptions entirely.

Validation

  • cargo fmt --all -- --check
  • git diff --check
  • cargo clippy -p omnikv-engine --tests --benches -- -D warnings
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test -p omnikv-engine --test panic_policy_audit -- --test-threads=1
  • cargo test -p omnikv-engine --test config_tests -- --test-threads=1
  • cargo test -p omnikv-engine --test storage_correctness -- --test-threads=1
  • cargo test -p omnikv-engine --test storage_tests -- --test-threads=1
  • cargo test -p omnikv-engine --test durability_evidence -- --test-threads=1
  • cargo test -p omnikv-engine --test operations -- --test-threads=1
  • cargo test -p omnikv-engine --test benchmarks --release -- --test-threads=1 --nocapture
  • rg -n "^#!\\[expect\\(" crates/omnikv-engine/tests crates/omnikv-engine/benches -g "*.rs" returned no matches.

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@SBALAVIGNESH123, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: be6e8193-6ec1-4b4b-a21c-b70f651de79c

📥 Commits

Reviewing files that changed from the base of the PR and between f4b1d63 and 44404e0.

📒 Files selected for processing (23)
  • crates/omnikv-engine/benches/omni_bench.rs
  • crates/omnikv-engine/benches/scan_buffer_pool.rs
  • crates/omnikv-engine/benches/volcano_dispatch.rs
  • crates/omnikv-engine/tests/anomaly_demos.rs
  • crates/omnikv-engine/tests/api_error_sanitization_tests.rs
  • crates/omnikv-engine/tests/benchmarks.rs
  • crates/omnikv-engine/tests/concurrent_stress.rs
  • crates/omnikv-engine/tests/config_tests.rs
  • crates/omnikv-engine/tests/crash_consistency.rs
  • crates/omnikv-engine/tests/debug_compaction.rs
  • crates/omnikv-engine/tests/debug_compaction_200.rs
  • crates/omnikv-engine/tests/debug_reopen.rs
  • crates/omnikv-engine/tests/durability_evidence.rs
  • crates/omnikv-engine/tests/operations.rs
  • crates/omnikv-engine/tests/ops_maturity.rs
  • crates/omnikv-engine/tests/panic_policy_audit.rs
  • crates/omnikv-engine/tests/raft_cluster.rs
  • crates/omnikv-engine/tests/sql_layer.rs
  • crates/omnikv-engine/tests/sql_v3_features.rs
  • crates/omnikv-engine/tests/storage_correctness.rs
  • crates/omnikv-engine/tests/storage_engine.rs
  • crates/omnikv-engine/tests/storage_perf.rs
  • crates/omnikv-engine/tests/storage_tests.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch agent/narrow-clippy-expect-scopes

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

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

@SBALAVIGNESH123
SBALAVIGNESH123 merged commit f3baa2b into master Jul 11, 2026
11 checks passed
@SBALAVIGNESH123
SBALAVIGNESH123 deleted the agent/narrow-clippy-expect-scopes branch July 11, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant