testing: allocs not reset for single-cycle runs #20590
Closed
Labels
Milestone
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Observe that it's not just a question of getting enough iterations for the division to work: 1168 allocs / 100 iterations = 11 allocs/op, but it is correctly reported as 0 in the first run. Something somewhere is not getting reset correctly. (The iterations does explain the variance in ns/op, but not allocs/op.)
I noticed this with tiny benchtimes and the runtime, but this could also impact benchmarks that run for longer than a second.
Reproduces with 1.8, although it is much less extreme:
Unclear whether this counts as a regression or not.
cc @mpvl
The text was updated successfully, but these errors were encountered: