Desktop UI benchmark: update metrics to the latest change Recent changes to custom metric does not require a custom_metric: prefix to the trace events. Metrics are defined inside the story definition instead. The CL also adds feature prefix(e.g. tab_search: webui_tab_strip:) to the js reported events. This will help to narrow down problems found by the auto-triage report. Also rename :benchmark_begin, :benchmark_end and :benchmark_value to :metric_begin, :metric_end and :metric_value to avoid confusion with the term "benchmark" in telemetry. Related CLs: https://chromium-review.googlesource.com/c/catapult/+/2953514 https://chromium-review.googlesource.com/c/catapult/+/2965033 Bug: 1201243 Change-Id: Ida3897961732c48e9525ecfdc9adc91425fbcae7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2954910 Commit-Queue: Yuheng Huang <yuhengh@chromium.org> Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by: Roman Arora <romanarora@chromium.org> Reviewed-by: John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#893703}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.