-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing: set up nightly run that runs fuzz tests #109680
Comments
Hi @RaduBerinde, please add a C-ategory label to your issue. Check out the label system docs. There was no T-eam label on the issue. Please add one so that the issue can be triaged by a team. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
blathers-crl
bot
added
X-blathers-untriaged
blathers was unable to find an owner
T-storage
Storage Team
labels
Aug 29, 2023
RaduBerinde
removed
the
X-blathers-untriaged
blathers was unable to find an owner
label
Aug 29, 2023
blathers-crl
bot
added
A-storage
Relating to our storage engine (Pebble) on-disk storage.
T-storage
Storage Team
labels
Aug 29, 2023
rickystewart
removed
A-storage
Relating to our storage engine (Pebble) on-disk storage.
T-storage
Storage Team
labels
Aug 29, 2023
we've added a fuzz test in #105654 also. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a couple of tests that use Go fuzzing infrastructure:
Fuzz tests only do something more interesting than regular tests when the
-fuzz
flag is used. We should set up a nightly run that does this.Jira issue: CRDB-31052
The text was updated successfully, but these errors were encountered: