Remove the recorded validation snapshot
The table was a one-off measurement on a particular machine. Keep the commands and the properties they check; readers can run them for current numbers.
This commit is contained in:
1 parent
fad9095062
commit
6e8f5175e2
1 file changed
-11
@@ -167,17 +167,6 @@ requires exact endpoints.
|
|||||||
`fuzz_raw` only checks memory safety and undefined behaviour for arbitrary
|
`fuzz_raw` only checks memory safety and undefined behaviour for arbitrary
|
||||||
(possibly unreadable) inputs.
|
(possibly unreadable) inputs.
|
||||||
|
|
||||||
One representative validation run on this machine:
|
|
||||||
|
|
||||||
| check | cases / runs | result |
|
|
||||||
| --- | ---: | --- |
|
|
||||||
| literal vs. Lean golden vectors | 40,000 | 0 mismatches (exact endpoints) |
|
|
||||||
| fast vs. literal on sorted corpus | 18,971 | 0 mismatches |
|
|
||||||
| extreme-offset regression (`extreme_test`) | 7,574 | 0 mismatches |
|
|
||||||
| finite readable sweep (`sweep_test`) | 13,565,772 | 0 mismatches |
|
|
||||||
| readable differential fuzzing (60 s) | 1,182,424 | 0 mismatches |
|
|
||||||
| raw safety fuzzing (60 s) | 1,905,270 | no ASan/UBSan findings |
|
|
||||||
|
|
||||||
`extreme_test` covers offsets the fuzzers deliberately avoid (they draw offsets
|
`extreme_test` covers offsets the fuzzers deliberately avoid (they draw offsets
|
||||||
from `[-256, 255]`). Both implementations decide the closed form's
|
from `[-256, 255]`). Both implementations decide the closed form's
|
||||||
`keyAfterN n k < upper` test from the key lengths (`keyAfterNLt`) rather than
|
`keyAfterN n k < upper` test from the key lengths (`keyAfterNLt`) rather than
|
||||||
|
|||||||
Reference in new issue
Block a user