If running a benchmark with --ignore-failure, it might be interesting to know if some of the commands actually failed.

For example, consider a long running compile-time benchmark:

hyperfine \
  --runs 3 \
  --ignore-failure \
  --parameter-list git_tag "v0.1,v0.2,v0.3,v0.4,v0.4.1,v0.5" \
  --prepare "git checkout --force {git_tag}; make clean" \
  --export-json "compile_time.j

There are many places in the documentation where we use:

• obsolete APIs (e.g. https://benchmarkdotnet.org/articles/configs/configs.html#object-style)
• APIs that have been changed (e.g. https://benchmarkdotnet.org/articles/configs/jobs.html#object-style).

Currently, I don't have enough time to address all of them.

In #466 a description about how to "disable" CPU performance scaling on Linux was added. It works by setting the cpufreq governor to performance (which is arguably not the only way to stabilize CPU frequency) and, later after the benchmark is done, setting that to powersave.

I personally think it's more appropriate to memorize what the previous governor was by a simple shell variable, and l