Pull in parts of the fuzzing branch #127
Merged
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
brson
force-pushed
the
fuzz-upstream
branch
from
d91653c
to
cd38f56
Compare
mootz12
approved these changes
Sep 11, 2023
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.
This brings in the rebased and cleaned up contents of the b-fuzz branch, except for two commits that change how overflows are handled within the contracts.
It includes changes to how the backstop rate is calculated.
The fuzzer in this branch can be run from within the test-suites directory with the command
At present this fuzzer will incorrectly fail on a variety of expected arithmetic overflows. Further patches in the b-fuzz branch change the contracts such that the fuzzer can distinguish these cases from unexpected panics.