Closed
Description
Version
main
Platform
n/a
Subsystem
benchmark
What steps will reproduce the bug?
One example: ./out/Release/node benchmark/run.js --format csv --filter randomInt -- crypto | wc -l
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
For the example, it should show 55 (as of this writing).
What do you see instead?
Depends on the timing, but I see somewhere between 40-42.
Additional information
684e107 seems to be the culprit as reverting the changes made there resolves the issue.
This seems to be affecting many different benchmarks/categories.
/cc @ShogunPanda