[llvm][cas] Implement a CAS stress tester #10606
Conversation
cachemeifyoucan
force-pushed
the
eng/llvm-cas-fuzzer
branch
from
383ee3a to
0efdf81
Compare
cachemeifyoucan
force-pushed
the
eng/llvm-cas-fuzzer
branch
from
0efdf81 to
bf37beb
Compare
cachemeifyoucan
changed the title
cachemeifyoucan
force-pushed
the
eng/llvm-cas-fuzzer
branch
from
bf37beb to
373b461
Compare
|
@swift-ci please test llvm |
There was a problem hiding this comment.
If we are going to name this "llvm-cas-test" would we expect other kinds of testing functionality to be in this tool? I'm thinking of llvm-cas -check-lock-files , since it's also more of a stress test than a general utility.
I'd also be fine keeping this focused on fuzzing, but then I would go back to llvm-cas-fuzzer or similar name.
The name change is because I removed the libfuzzer dependency as I only using the coverage guided random input generation which I don't think add any value. I guess we can still call it |
This is a basic tester for CAS ObjectStore that will insert random data into CAS and validate with several configurations randomly generated. It will check: * multi-threaded insertion * multi-process insertion * try randomly kill the subprocesses that are inserting data And make sure it doesn't leave CAS in an invalid state. Suggested usage: ``` LLVM_CAS_LOG=2 llvm-cas-test --cas=... --print-config ```
cachemeifyoucan
force-pushed
the
eng/llvm-cas-fuzzer
branch
from
373b461 to
b804c9c
Compare
|
@swift-ci please test llvm |
This is a basic tester for CAS ObjectStore that will insert random data into CAS and validate with several configurations randomly generated. It will check:
And make sure it doesn't leave CAS in an invalid state. Suggested usage: