[Pixel Diff Ash] Include version numbers in benchmark names Benchmark image names should include version numbers. For example, when attempting to add a benchmark image whose name is Foo, the developer should use "Foo.rev_0" instead of "Foo". In addition, always increase the version number by 1 after each update on benchmarks. For example, developer attempts to update the benchmark "Foo.rev_0", after update, the benchmark name should be "Foo.rev_1" instead of "Foo.rev_0". This CL does not introduce any differences in product code. Bug: 1383191 Change-Id: I04171b67d94b68d9b36f2aa55e29d66751052b1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4016857 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Andrew Xu <andrewxu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1069881}
Chromium 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.