Improve fuzz target orchestration#816
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Motivation
fuzz/fuzz_targets/*.rsandfuzz/Cargo.tomlso newly added harnesses are not omitted from CI or PR evidence.Description
xtask fuzz:--listto print manifest-declared fuzz targets and--allto run every declared target, and keeprsa_pkcs8_pem_parseas the default when no target is given (DEFAULT_FUZZ_TARGET).list_fuzz_targets()by parsingfuzz/Cargo.toml, verifying each[[bin]]entry, and rejecting undeclaredfuzz_targets/*.rssources.ensure_cargo_fuzz_available()so--listcan run withoutcargo-fuzzinstalled while real fuzz runs still fail fast if missing.fuzz_pr) tocargo fuzz buildall harnesses for compile coverage then run a bounded smoke subset viais_pr_fuzz_target()to skip expensive keygen or chain-building harnesses.is_pr_fuzz_target()to exclude expensive targets and extendxtaskunit tests to cover manifest-backed discovery, manifest-drift detection, PR-target filtering, and list behavior.Testing
cargo test -p xtask fuzz -- --nocaptureandcargo test -p xtask fuzz_targets -- --nocaptureand all xtask unit tests related to fuzz discovery and filtering passed.cargo run -p xtask -- fuzz --listto exercise the new listing path and it printed the declared fuzz targets (manifest-backed); this succeeded.cargo check -p xtaskto verify compilation and static checks; this succeeded.Codex Task