LRU fuzzing overhaul #57
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
lru: simplify paranoid GC Linked List testing
Move the
paranoidLLconstant to its own build-tagged files so we cantoggle which mode is active by setting a build-tag on the test instead
of having to use sed to modify the constant-value.
lru: rewrite FuzzTypedAddRemove
Vastly simplify FuzzTypedAddRemove by limiting the keyspace, and make it
more useful by providing triggers for running the GC in parallel.
Use the two high-bits to select the operation and the low-6 bits the
key. (this eliminates the degree of freedom where the fuzzer picks
super-long keys, since it's effectively fuzzing the hash-table's
hash-function.)
Unfortunately, this does cause the fuzzer to explore the control flow in
the Garbage Collector somewhat, (that's an unfortunate random walk),
but when working with weak pointers, you really do need the GC to run to
have any confidence that you didn't remove something you need.