andrew
de47aa53b0
Add to corpus
2024-09-05 16:24:41 -07:00
andrew
cb6e4292f2
Add to corpus
2024-08-26 14:33:16 -07:00
andrew
8a04e57353
Add to corpus
2024-08-22 16:52:33 -07:00
andrew
dfa178ba19
Add to corpus (from fuzzing on macos)
2024-08-20 13:32:04 -07:00
andrew
f11720f5ae
Add to corpus
2024-08-19 21:52:47 -07:00
andrew
aa8504ddba
Add to corpus
2024-08-15 18:47:47 -07:00
andrew
479b39d055
Add to corpus
2024-08-12 17:28:19 -07:00
andrew
e3d1b2e842
Add to corpus
...
After a bunch of fuzzing on "udon" (my new zen4 machine)
2024-08-09 19:48:22 -07:00
andrew
9f8800af16
Add more to corpus (from fuzzing on osx)
...
Maybe we should just accumulate the corpus instead of replacing it? That
should be easier on git right?
2024-08-09 18:06:54 -07:00
andrew
9b56a74b2f
Update corpus
2024-08-06 17:43:48 -07:00
andrew
8e480528d5
Update corpus
2024-08-01 14:56:36 -07:00
andrew
79410d071f
Add accidentally-deleted corpus back
2024-07-26 14:57:04 -07:00
andrew
55271ad06c
Update corpus
...
To match new "interleaving" test setup
2024-07-23 16:54:03 -07:00
andrew
60cb274a15
Update corpus
2024-07-10 18:49:41 -07:00
andrew
76df63a9d7
Allow writeVersion, oldestVersion, and readVersion to span 2e9
2024-07-03 14:19:50 -07:00
andrew
88bcc7b75c
Update corpus
2024-07-03 09:36:03 -07:00
andrew
2646d5eaf1
Get back to 100% coverage
...
Closes #30
This is achieved by running libfuzzer with USE_32_BIT_VERSIONS={OFF,ON},
and then combining the corpora. I suspect that the problem earlier was
that we only had the 32 bit corpus but were measuring coverage for 64
bit in jenkins.
2024-06-30 21:15:42 -07:00
andrew
a2bf839b19
Update corpus
2024-06-27 17:15:35 -07:00
andrew
c13dc88ff4
Update corpus
2024-04-22 15:24:55 -07:00
andrew
bf91bca16d
Include long common prefix in fuzz test
2024-04-18 12:43:48 -07:00
andrew
a5710b8282
Remove performance-only code from debug build for increased coverage
2024-03-18 16:21:55 -07:00
andrew
f2b5e9b0bf
Change max key len to 8, update corpus
...
Now that we don't have a fixed buffer reserved for partial key bytes,
there's nothing (obvious) that makes testing short versus long keys much
different. maybeDecreaseCapacity is an exception, and we'll write some
tests covering that manually.
2024-03-18 11:55:43 -07:00
andrew
b0ac7e41b9
Update corpus
2024-03-12 14:52:43 -07:00
andrew
987e93b190
Update corpus
2024-03-07 18:31:04 -08:00
andrew
bd5d0259d9
Update corpus
2024-02-21 22:13:57 -08:00
andrew
cb2f66b4b7
Remove a check from setOldestVersion
2024-02-19 16:20:04 -08:00
andrew
cb31f4c25b
Fix bugs
2024-02-17 22:09:00 -08:00
andrew
e30922ab9c
Update corpus
2024-02-15 16:14:03 -08:00
andrew
35a3289ab9
Simplify and fix bugs
2024-02-09 22:45:38 -08:00
andrew
b663325991
Update corpus
2024-02-08 10:06:23 -08:00
andrew
9a80c96533
Short circuit point reads based on maxVersion
2024-02-06 14:38:39 -08:00
andrew
2d220a3f7d
Update corpus
2024-02-03 20:15:31 -08:00
andrew
20bd5c2fa6
More corpus tinkering. Missing coverage for Node256
2024-02-01 18:22:45 -08:00
andrew
906c53ea63
Update corpus
2024-02-01 16:58:42 -08:00
andrew
802615e38b
Update corpus
2024-02-01 11:47:13 -08:00
andrew
0eff5628bd
Fix lastLeq bug
2024-02-01 11:24:57 -08:00
andrew
e84ea10d20
Update corpus
2024-01-31 11:27:32 -08:00
andrew
dad3a8b5ad
Update corpus
2024-01-30 15:34:23 -08:00
andrew
df3b2b8696
Update corpus
2024-01-24 13:16:05 -08:00
andrew
77ce12e070
Add corpus of tests
2024-01-24 10:49:46 -08:00
andrew