Issue metadata
Sign in to add a comment
|
crostc_perf: cannot parse json files |
||||||||||||||||||||||
Issue descriptionIt appears that the format of telemetry result files have changed and they no longer have the fields with __http://* suffixes. This causes crostsc_perf to complain about duplicate fields. Rahul suggested (in IRC) to delete the logic pertaining to detailed results and just do the summary since no one is looking at detailed results
,
Jun 13 2018
AFAIK, detailed results include ALL of the metrics generated by the benchmark. But our dashboards however track only a smaller number of metrics (summarized results). Lets say in future, we want to track a new metric X (for an existing benchmark) in our dashboards. Dropping detailed changes will prevent us from getting the old data about X. (Not entirely correct since we also keep the original json files around. So we can regenerate CIO files with the data for metric X in theory).
,
Jun 14 2018
I would prefer we keep the detailed results.
,
Jun 14 2018
I just submitted cl/200579858 that only skips detailed results for the benchmark smoothness.tough_webgl_cases. Rest of the benchmarks are unaffected. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lloz...@google.com
, Jun 12 2018