Narrow clippy expectations in tests - #72
Conversation
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (23)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
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
#![expect(...)]file-level clippy expectations fromcrates/omnikv-engine/testsandcrates/omnikv-engine/benches.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 -- --checkgit diff --checkcargo clippy -p omnikv-engine --tests --benches -- -D warningscargo clippy --workspace --all-targets -- -D warningscargo test -p omnikv-engine --test panic_policy_audit -- --test-threads=1cargo test -p omnikv-engine --test config_tests -- --test-threads=1cargo test -p omnikv-engine --test storage_correctness -- --test-threads=1cargo test -p omnikv-engine --test storage_tests -- --test-threads=1cargo test -p omnikv-engine --test durability_evidence -- --test-threads=1cargo test -p omnikv-engine --test operations -- --test-threads=1cargo test -p omnikv-engine --test benchmarks --release -- --test-threads=1 --nocapturerg -n "^#!\\[expect\\(" crates/omnikv-engine/tests crates/omnikv-engine/benches -g "*.rs"returned no matches.