Add Exceptions For Transaction Fuzzer #12313
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
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.
What type of PR is this?
E2E Fix
What does this PR do? Why is it needed?
In #12270, we returned errors in our transaction fuzzer if a transaction wasn't able to be successfully completed. However due
to the nature of how the fuzzer constructs transactions, this would always be a possibility. The end result is that our e2e runs started failing much more often. This PR adds in exceptions for them so that we don't need to return errors if a transaction isn't valid.
Which issues(s) does this PR fix?
N.A
Other notes for review