GitLab

The script runs TBMv3 metric and the corresponding TBMv2 metric on
given traces and compare the results. If the metrics are equal than
the newly added TBMv3 metric is the same as the old TBMv2 metric.
If the results are different the script will output trace files and json
files (results of run_metric) so the user is able to debug analyse them.

Example usage:
tools/perf/validate_tbmv3_metric  --tbmv3-name=uma_metrics --tbmv3-histogram=graphics_smoothness_percent_dropped_frames_compositor_thread_universal --tbmv2-name umaMetric --tbmv2-histogram=Graphics.Smoothness.PercentDroppedFrames.CompositorThread.Universal

Now a path to a file with trace link is required. We plan to automate
the process of getting trace links in the future.
Metric units are also ignored in this change. We plan to integrate units
support later along with other fancy statistics about metric values.

For more information, see https://docs.google.com/document/d/1wI1gk5X2-eQk9-NLHSK_EgmVs-doyyodz0XtP7Pd15M/edit?usp=sharing

Change-Id: I4ca068357a9a0c0f9a5cd5267c64aa53acfe8513
Bug: 1128919
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413492Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Deep Roy <dproy@chromium.org>
Reviewed-by: Mikhail Khokhlov <khokhlov@google.com>
Commit-Queue: Julia Semavina <nuwanda@google.com>
Cr-Commit-Position: refs/heads/master@{#810851}