Dave, is there anything blocking us from ensuring that Pinpoint always uses histograms for chromium.perf and chromium.perf.fyi?
https://chromium-review.googlesource.com/c/chromium/src/+/1070219 flips the flag for the waterfalls, and Emily mentioned that we need to keep the logic that maybe appends --output-format=histograms until Pinpoint doesn't need to make a decision as to whether to use histograms or not.
Pinpoint has been using histograms exclusively for a few months already!
Pinpoint doesn't use that appending logic, it creates the test commands from scratch here:
https://chromium.googlesource.com/catapult.git/+/HEAD/dashboard/dashboard/pinpoint/models/quest/run_telemetry_test.py#13
Is `--output-format=histograms` becoming the default? We'll want to retain the flag in Pinpoint for a few months since we may bisect on old versions of Chromium/Catapult that may require the flag.
Thanks Dave. It's not becoming the default in the sense that Telemetry intends to output HistogramSet JSON if --output-format is not passed; HTML will remain the default.
That said, run_performance_tests now (as of the above CL) always appends --output-format=histograms as long as no other --output-format flag has been passed (e.g. by Pinpoint). It sounds like this is the sense in which you mean it, and if so, yes, I think it would be good to clean up the flag on the Pinpoint side in a few months and simplify the logic on the src side.
Filed https://bugs.chromium.org/p/chromium/issues/detail?id=848077 about cleaning this up.
Comment 1 by eakuefner@chromium.org
, Jul 17 2017