benchmark/tools/gbench/Inputs
Roman Lebedev 96d820f73f
tools/compare: don't actually discard valid (but zero) `pvalue` (#1733)
* tools/compare: when dumping json, pretty-print it

It's rather completely non-human-readable otherwise.
I can't imagine the filesize really matters,
and if it does, it should just be compressed later on.

* tools/compare: add failing test

* tools/compare: don't actually discard valid (but zero) `pvalue`

So, this is embarressing. For a very large number of repetitions,
we can end up with pvalue of a true zero, and it obviously compares false,
and we treat it as-if we failed to compute it...
2024-01-08 09:57:00 +00:00
..
test1_run1.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test1_run2.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test2_run.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test3_run0.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test3_run1.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test4_run.json compare.py: sort the results (#1168) 2021-06-03 16:22:52 +03:00
test4_run0.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test4_run1.json Revert "Add possibility to ask for libbenchmark version number (#1004) (#1403)" (#1417) 2022-06-20 17:52:03 +01:00
test5_run0.json tools/compare: don't actually discard valid (but zero) `pvalue` (#1733) 2024-01-08 09:57:00 +00:00
test5_run1.json tools/compare: don't actually discard valid (but zero) `pvalue` (#1733) 2024-01-08 09:57:00 +00:00