| commit | d9ea451ab6c11d548d3a11183fdbce49385f2e56 | |
| author | Christian Couder <christian.couder@gmail.com> | |
| Fri, 4 May 2018 12:36:36 +0000 (4 14:36 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 6 May 2018 04:04:54 +0000 (6 13:04 +0900) | ||
| tree | 1c818fa7fe49c5d0319e97141a930b4fdb982f6f | treesnapshot (tar.gz zip) |
| parent | 297e685cbaaa0d33125dc59ce2aa55f03a836598 | commitdiff |
perf/bisect_run_script: disable codespeed
When bisecting a performance regression using a config file,
`./bisect_regression --config my_perf.conf` for example, the
config file can contain Codespeed configuration which would
instruct the 'aggregate.perl' script called by the 'run'
script to output results in the Codespeed format and maybe
to try to send this output to a Codespeed server.
This is unfortunate because the 'bisect_run_script' relies
on the regular output from 'aggregate.perl' to mesure
performance, so let's disable Codespeed output and sending
results to a Codespeed server.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When bisecting a performance regression using a config file,
`./bisect_regression --config my_perf.conf` for example, the
config file can contain Codespeed configuration which would
instruct the 'aggregate.perl' script called by the 'run'
script to output results in the Codespeed format and maybe
to try to send this output to a Codespeed server.
This is unfortunate because the 'bisect_run_script' relies
on the regular output from 'aggregate.perl' to mesure
performance, so let's disable Codespeed output and sending
results to a Codespeed server.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/perf/bisect_run_script | diffblobblamehistory |