A few ideas from tdulcet/Benchmarking-Tool#1:

• Show the actual exit code if a command fails and -i, --ignore-failure is not set
• Think about adding the median runtime between min and max. This would be easy to implement, but I don't really like that the output width becomes even larger. Open for ideas.

When I have a MsBuildArgument whose value ends in a backslash, there is an error somewhere along the intermediate code generation that causes the generated program to receive malformed arguments, resulting in a parsing exception. Here's an example of such:

var summary = BenchmarkRunner.Run<MyBenchmark>(DefaultConfig.Instance
    .AddJob(Job.Default
        .WithArguments(new[]
     

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