Fuzz meas fixes #45
Merged
Fuzz meas fixes #45
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
Codecov Report
@@ Coverage Diff @@
## master #45 +/- ##
==========================================
+ Coverage 99.87% 99.97% +0.09%
==========================================
Files 5 5
Lines 4111 4129 +18
==========================================
+ Hits 4106 4128 +22
+ Misses 5 1 -4 |
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.
Some fixes for the fuzzing failures from the new measurement fuzzing tests.
This may be first of a few of these fixes.
This one splits the power operation interpretation and imposes a few extra conditions that were otherwise resulting in a series of cascading repeated failures. The condition imposed was restrict that only numbers could be multiplied by powers greater than 7.
Previously it also was failing to take powers and was instead interpreting them as multiples.
This was only in the case of things like
^(3)^(3)^(3)^(3). The first power was always interpreted correctly.