You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though it is a good thing to show warnings for unstable results (:wavy_dash: ... (Unstable with ...), sometimes one wants to run benchmarks in an environment where the execution is potentially perturbed by other processes and so results are known to be unstable; for example, in continuous integration.
So, it might be handy if an environment variable (NANOBENCH_NO_UNSTABLE_WARNING or something) could change the behaviour and suppress warnings for unstable results.
Changing the behaviour by a command-line option could be an alternative way, but I think an environment variable is more suitable for CI, and I guess it is easier to implement.
The text was updated successfully, but these errors were encountered:
Sounds like a good idea. I think I'll add an environment variable NANOBENCH_SUPPRESS_WARNINGS to do this and also suppress the other warnings like for frequency scaling
Though it is a good thing to show warnings for unstable results (
:wavy_dash: ... (Unstable with ...
), sometimes one wants to run benchmarks in an environment where the execution is potentially perturbed by other processes and so results are known to be unstable; for example, in continuous integration.So, it might be handy if an environment variable (
NANOBENCH_NO_UNSTABLE_WARNING
or something) could change the behaviour and suppress warnings for unstable results.Changing the behaviour by a command-line option could be an alternative way, but I think an environment variable is more suitable for CI, and I guess it is easier to implement.
The text was updated successfully, but these errors were encountered: