benchmark/tools/gbench
Matt Armstrong 6bc17754f6
Support --benchmarks_filter in the compare.py 'benchmarks' command (#1486)
Previously compare.py ignored the --benchmarks_filter
argument when loading JSON.  This defeated any workflow when
a single run of the benchmark was run, followed by multiple
"subset reports" run against it with the 'benchmarks'
command.

Concretely this came up with the simple case:

 compare.py benchmarks a.json b.json --benchmarks_filter=BM_Example

This has no practical impact on the 'filters' and
'benchmarkfiltered' comand, which do their thing at a later
stage.

Fixes #1484

Co-authored-by: dominic <510002+dmah42@users.noreply.github.com>
2023-02-06 16:57:07 +00:00
..
Inputs Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
__init__.py
report.py Stop using pandas.Timedelta (fixes #1482) (#1483) 2022-09-08 20:26:58 +03:00
util.py Support --benchmarks_filter in the compare.py 'benchmarks' command (#1486) 2023-02-06 16:57:07 +00:00