88bcc7b75c
Update corpus
Tests / Clang total: 1305, failed: 47, passed: 1258
Tests / SIMD fallback total: 1305, failed: 47, passed: 1258
Tests / 32-bit versions total: 1305, failed: 47, passed: 1258
Tests / Release [gcc] total: 1305, failed: 47, passed: 1258
weaselab/conflict-set/pipeline/head There was a failure building this commit
2024-07-03 09:36:03 -07:00
2646d5eaf1
Get back to 100% coverage
...
Tests / Clang total: 1776, failed: 232, passed: 1544
Tests / SIMD fallback total: 1776, failed: 232, passed: 1544
Tests / 32-bit versions total: 1776, failed: 232, passed: 1544
Tests / Release [gcc] total: 1776, failed: 232, passed: 1544
Tests / Release [gcc,aarch64] total: 1327, failed: 116, passed: 1211
Tests / Coverage total: 1333, failed: 233, passed: 1100
weaselab/conflict-set/pipeline/head There was a failure building this commit
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
a2bf839b19
Update corpus
2024-06-27 17:15:35 -07:00
c13dc88ff4
Update corpus
2024-04-22 15:24:55 -07:00
bf91bca16d
Include long common prefix in fuzz test
2024-04-18 12:43:48 -07:00
a5710b8282
Remove performance-only code from debug build for increased coverage
2024-03-18 16:21:55 -07:00
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
b0ac7e41b9
Update corpus
2024-03-12 14:52:43 -07:00
987e93b190
Update corpus
Tests / Release [gcc] total: 827, passed: 827
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend
|:-:|:-:|:-:|:-:|:-:
|0|0|0|0|:clap:
Tests / Release [gcc,aarch64] total: 826, passed: 826
Tests / Coverage total: 825, passed: 825
weaselab/conflict-set/pipeline/head This commit looks good
2024-03-07 18:31:04 -08:00
bd5d0259d9
Update corpus
2024-02-21 22:13:57 -08:00
cb2f66b4b7
Remove a check from setOldestVersion
2024-02-19 16:20:04 -08:00
cb31f4c25b
Fix bugs
Tests / Release [gcc] total: 423, passed: 423
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend
|:-:|:-:|:-:|:-:|:-:
|0|0|0|0|:clap:
Reference build: <a href="https://jenkins.weaselab.dev/job/weaselab/job/conflict-set/job/main/17//gcc">weaselab » conflict-set » main #17</a>
Tests / Coverage total: 421, passed: 421
weaselab/conflict-set/pipeline/head This commit looks good
2024-02-17 22:09:00 -08:00
e30922ab9c
Update corpus
2024-02-15 16:14:03 -08:00
35a3289ab9
Simplify and fix bugs
Tests / Release [gcc] total: 363, failed: 2, passed: 361
Tests / Coverage total: 361, passed: 361
weaselab/conflict-set/pipeline/head There was a failure building this commit
2024-02-09 22:45:38 -08:00
b663325991
Update corpus
2024-02-08 10:06:23 -08:00
9a80c96533
Short circuit point reads based on maxVersion
Tests / Release [gcc] total: 337, passed: 337
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend
|:-:|:-:|:-:|:-:|:-:
|0|0|0|0|:clap:
Reference build: <a href="https://jenkins.weaselab.dev/job/weaselab/job/conflict-set/job/main/5//gcc">weaselab » conflict-set » main #5</a>
Tests / Coverage total: 335, passed: 335
weaselab/conflict-set/pipeline/head This commit looks good
2024-02-06 14:38:39 -08:00
2d220a3f7d
Update corpus
2024-02-03 20:15:31 -08:00
20bd5c2fa6
More corpus tinkering. Missing coverage for Node256
2024-02-01 18:22:45 -08:00
906c53ea63
Update corpus
2024-02-01 16:58:42 -08:00
802615e38b
Update corpus
2024-02-01 11:47:13 -08:00
0eff5628bd
Fix lastLeq bug
2024-02-01 11:24:57 -08:00
e84ea10d20
Update corpus
2024-01-31 11:27:32 -08:00
dad3a8b5ad
Update corpus
2024-01-30 15:34:23 -08:00
df3b2b8696
Update corpus
2024-01-24 13:16:05 -08:00
77ce12e070
Add corpus of tests
2024-01-24 10:49:46 -08:00
