Adjust fuzzing configs to match what's in QuickJS #836
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.
Description of the change
Adding some parameters to the Javy library crate's
Config
so we can set them to non-default values when fuzzing. Also updating the fuzzer to set those parameters. Also throwing any fuzzing inputs with more than 350{
characters.Note that the fuzzer still crashes with out of memory errors with this change.
Why am I making this change?
We see out of memory errors when running the fuzzer continuously. This updates a few configs to match what's in QuickJS's fuzzer. I also don't try to run strings with more than 350
{
characters because that trips the maximum stack size. We should consider investigating that further but I'd like to at least get the fuzzer running continuously.Checklist
javy-cli
andjavy-plugin
do not require updating CHANGELOG files.