We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, we do 3 retries when a benchmark fails. This is really useful for racy implementations.
Though, it's just a time waster for most predictable sequential benchmarks.
The number of retries be an option in the configuration file, and as a command line parameter.
The text was updated successfully, but these errors were encountered:
I decided against making it a command-line parameter, in the interest of having a complete documentation of the experiments.
Sorry, something went wrong.
Implemented with #108.
No branches or pull requests
Currently, we do 3 retries when a benchmark fails.
This is really useful for racy implementations.
Though, it's just a time waster for most predictable sequential benchmarks.
The number of retries be an option in the configuration file, and as a command line parameter.
The text was updated successfully, but these errors were encountered: