Fuzzing with the random numbers passed from the config file #38
Conversation
This file contains 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
hmeriann
force-pushed
the
randoms-config
branch
2 times, most recently
from
8c37be4
to
c06257e
Compare
hmeriann
force-pushed
the
randoms-config
branch
from
c06257e
to
7d56f94
Compare
Tmonster
reviewed
Sep 30, 2024
Tmonster
reviewed
Sep 30, 2024
…h default values false, 1000, 120 respectfully; split up the Fuzz job to don't exclude to many parameters
…th default values
… the fuzz_duckdb workflow
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.
As it describes in the duckdb/duckdb_sqlsmith#23, we'd like the fuzzer to follow a specific path to generate statements, functions etc.
This PR makes
cifuzzto fuzz with and without the values defined in configuration file.