2 Commits

Author	SHA1	Message	Date
Roman Lebedev	58588476ce	Track two more details about runs - the aggregate name, and run name. (#675) ... This is related to @BaaMeow's work in https://github.com/google/benchmark/pull/616 but is not based on it. Two new fields are tracked, and dumped into JSON: * If the run is an aggregate, the aggregate's name is stored. It can be RMS, BigO, mean, median, stddev, or any custom stat name. * The aggregate-name-less run name is additionally stored. I.e. not some name of the benchmark function, but the actual name, but without the 'aggregate name' suffix. This way one can group/filter all the runs, and filter by the particular aggregate type. I *might* need this for further tooling improvement. Or maybe not. But this is certainly worthwhile for custom tooling.	2018-09-13 15:08:15 +03:00
Roman Lebedev	c614dfc0d4	*Display* aggregates only. (#665) ... There is a flag d9cab612e4/src/benchmark.cc (L75-L78) and a call d9cab612e4/include/benchmark/benchmark.h (L837-L840) But that affects everything, every reporter, destination: d9cab612e4/src/benchmark.cc (L316) It would be quite useful to have an ability to be more picky. More specifically, i would like to be able to only see the aggregates in the on-screen output, but for the file output to still contain everything. The former is useful in case of a lot of repetition (or even more so if every iteration is reported separately), while the former is **great** for tooling. Fixes https://github.com/google/benchmark/issues/664	2018-09-12 16:26:17 +03:00