commit | 1e99bff85c89e20d9ec64975816a4cf5e20708b7 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Oct 31 12:27:20 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 31 12:27:20 2024 |
tree | ed7b6dd6124db70e47c44abfb3e7ff34ff493723 | |
parent | 7a43315d7edb3ebe774e74496e58103c6838af03 [diff] |
Roll Crossbench from 2483b62b68ca to 7dec2865a6c0 (1 revision) https://chromium.googlesource.com/crossbench.git/+log/2483b62b68ca..7dec2865a6c0 2024-10-31 cbruni@chromium.org Strip benchmark name in story name If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/crossbench-chromium Please CC cbruni@google.com,crossbench@chromium.org,johnchen@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: johnchen@google.com Change-Id: Ia23aa336883ce598b73ff5111ba907ae35c14db7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5982653 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1376244}
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.