- xtask looked for target/release/printcraft-cli even under CARGO_TARGET_DIR (which parallel agents use), and a child that failed to spawn counted as a pass: such runs fuzzed nothing and reported 0 crashes. The binary now comes from CARGO_TARGET_DIR (gates' corpus check and text oracle too), and fuzz stops if it is missing. - On Linux each child runs under a 4 GiB address-space limit, so an input that allocates without bound becomes a crash finding instead of exhausting the machine: the nightly fuzz job's runner was killed this way every night, losing the findings. Allocation failures are kept as the finding's message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| baselines | ||
| src | ||
| Cargo.toml | ||