kvnemesis: first step towards a fuzzed KVNemesis #148634
Open
+146
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is |
You can run this test with the go fuzzer with something like: go test ./pkg/kv/kvnemesis/ -test.fuzz=FuzzKVNemesisSingleNode \ -test.fuzzcachedir=_fuzzcache -v -test.run=^$ \ -tags crdb_test -timeout=300m -parallel=4 It can also be run under bazel, but I have not yet sorted out all of the flags needed to get a coverage enabled build and to ensure that the failing test cases get written somewhere that can be referenced on subsequent runs. The idea here is that the fuzzer provides a []byte that then determines the output of all random decisions in KVNemesis. This doesn't account for metamorphic decisions made outside of KVNemesis. KVNemesis is a rather heavyweight test which seemed to be a problem for running it reliably under go-fuzz; however, go-fuzz's poor diagnostics when the test worker crash has made it hard to determine the exact cause so far. Epic: none Release note: None
stevendanna
force-pushed
the
ssd/kvnemesis-fuzz
branch
from
9a180d0 to
616d692
Compare
srosenberg
added a commit
to srosenberg/cockroach
that referenced
this pull request
Jun 23, 2025
To run natively, ``` go build -buildmode=c-archive -gcflags=all=-d=libfuzzer -tags "crdb_test,gofuzz,gofuzz_libfuzzer,libfuzzer" -trimpath -gcflags syscall=-d=libfuzzer=0 -o kvnemesis_fuzz.a pkg/kv/kvnemesis/main/main.go clang -o kvnemesis_fuzz kvnemesis_fuzz.a /home/stan_cockroachlabs_com/go/src/github.com/cockroachdb/cockroach/bin/c-deps/archived_cdep_libjemalloc_linux/lib/libjemalloc.a /home/stan_cockroachlabs_com/go/src/github.com/cockroachdb/cockroach/bin/c-deps/archived_cdep_libproj_linux/lib/libproj.a -fsanitize=fuzzer ./kvnemesis_fuzz -max_len=8192 seeds >libfuzzer.out 2>&1 ``` To run in go with libfuzzer instrumentation, ``` bazel run --override_repository=io_bazel_rules_go=/home/stan_cockroachlabs_com/go/src/github.com/cockroachdb/rules_go --@io_bazel_rules_go//go/config:gc_goopts=-d=libfuzzer --crdb_test pkg/kv/kvnemesis:kvnemesis_test -- -test.run notests -test.fuzz FuzzKVNemesisSingleNode -test.fuzzcachedir /tmp/foobar/ -test.v >gofuzzer.out 2>&1 ``` [1] cockroachdb#148634 [2] https://cockroachlabs.slack.com/archives/C023S0V4YEB/p1750542607409039?thread_ts=1750341116.758639&cid=C023S0V4YEB Epic: none Release note: None
|
Test failure is unrelated (but important and fixed here #148660) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
You can run this test with the go fuzzer with something like:
go test ./pkg/kv/kvnemesis/ -test.fuzz=FuzzKVNemesisSingleNode
-test.fuzzcachedir=_fuzzcache -v -test.run=^$
-tags crdb_test -timeout=300m -parallel=4
It can also be run under bazel, but I have not yet sorted out all of the flags needed to get a coverage enabled build and to ensure that the failing test cases get written somewhere that can be referenced on subsequent runs.
The idea here is that the fuzzer provides a []byte that then determines the output of all random decisions in KVNemesis. This doesn't account for metamorphic decisions made outside of KVNemesis.
KVNemesis is a rather heavyweight test which seemed to be a problem for running it reliably under go-fuzz; however, go-fuzz's poor diagnostics when the test worker crash has made it hard to determine the exact cause so far.
Epic: none
Release note: None