test(format): keep the 2026-09-20 B-tree v2 fuzz crash as a regression

Browse Source

An 82-byte fuzz_btree_v2 crash input from 2026-09-20 was left untracked
in fuzz/artifacts. Replayed today it runs cleanly: the depth cap and
record budget added to B-tree v2 traversal that day fixed it. It is now
in the committed fuzz corpus, and a robustness test replays the fuzz
target's exact code path on it so a regression fails CI rather than
waiting for someone to run the fuzzer.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

...

This commit is contained in:

osobh

2026-09-25 20:38:34 -05:00

co-authored by Claude Opus 5.5

parent 75bdb53342

commit 46203ea761

2 changed files with 46 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

crates/clawhdf5-format/fuzz/corpus/fuzz_btree_v2/regression-crash-f98c19dc

BIN

Binary file not shown.