cmd/evm: don't reuse state between iterations, show errors #30780
+14
−9
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
…enchmark errors are captured and printed to output.
jwasinger
requested review from
holiman,
MariusVanDerWijden and
lightclient
as code owners
holiman
reviewed
Nov 21, 2024
Co-authored-by: Martin HS <[email protected]>
jwasinger
commented
Nov 22, 2024
holiman
changed the title
Co-authored-by: Martin HS <[email protected]>
Co-authored-by: Martin HS <[email protected]>
Co-authored-by: Martin HS <[email protected]>
Co-authored-by: Martin HS <[email protected]>
holiman
reviewed
Nov 25, 2024
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.
Reusing state between benchmark iterations resulted in inconsistent results across runs, which surfaced in #30778 .
If these errors are triggered again, they should be printed to output. To ensure that the code invoking
testing.Benchmark()can catch and output these errors, and then exit: I replace calls tot.B.Fatalfwith setting an error which is consumed by the calling code.The same consistency checks should probably be applied to the state test benchmarker. I am figuring that out now.
closes #30778 .