mirror of https://github.com/google/benchmark.git
6bc17754f6
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> |
||
|---|---|---|
| .. | ||
| gbench | ||
| BUILD.bazel | ||
| compare.py | ||
| libpfm.BUILD.bazel | ||
| requirements.txt | ||
| strip_asm.py | ||