cmd/evm: don't reuse state between evm benchmark iterations. ensure benchmark errors are included in output. #30780
+18
−12
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.Fatalf
with 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 .