Improve array len fuzzing#495
Merged
Merged
Conversation
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## master #495 +/- ##
=======================================
Coverage 98.14% 98.14%
=======================================
Files 78 78
Lines 10308 10308
=======================================
Hits 10117 10117
Misses 191 191 ☔ View full report in Codecov by Sentry. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
And yet another attempt at fixing array len fuzzing so we won't overload the fuzzer with OOM or timeouts. Now, the array length is produced like a Vec len but only once for the first instantiation.
To ensure that
[[(); N]; M]costs the fuzzerNxMunits of input instead of justN+M, the arbitrary value production now imposes a minimal penalty on unit/empty values. While this wastes some input, it (hopefully) ensures that the fuzzed values do not explode, since they are bounded by the input.* [ ] I've included my change inCHANGELOG.md