Fix #315: JTest uses a flawed RNG setup #347
Merged
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.
Summary:
This PR addresses issue #315 by replacing
JPerfUtils
withJBenchUtils
, transitioning from standalone functions to a class-based format. The seed for the RNG is now set inside theJBenchUtils
constructor using the event number and caller name passed to the constructor.Changes:
JPerfUtils
withJBenchUtils
.JBenchUtils
is now a class that encapsulates the RNG.JBenchUtils
constructor, ensuring it is set based on the event number and caller name, enhancing reproducibility and eliminating the need for the previous thread-local workaround.Benefits:
JPerfUtils
.Related Issue:
Testing: