Fix to change expected of test according to build tag #528
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
The mismatch between the constant VrfProofSize and the result of the function GenerateVRFProof() as well as the constant VrfOutputSize and the result of the function VRFVerify() will lead to the failure of the benchmark test, benchmarkVRFProof().
I fixed the constants VrfProofSize and VrfOutputSize to change according to the build tag and to invert the expected and actual values passed in the function require.Equalf().