commit | e5642e6044609c55fa8a70ce7f2be7c29ce1099e | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Aug 08 13:09:10 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 08 13:09:10 2025 |
tree | 03a6a765fc2de85b16c0035e75f446c80b0e7e4e | |
parent | 735163f9ad69c71ebd64ad93daea93499e6e9963 [diff] |
Roll Chrome Android ARM64 Orderfile from 8L6CWya3z3oqJCxk1... to nvqVjGsOmaTw3xfsI... If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/orderfile-android-arm64-chromium Please CC clank-build@google.com,clank-library-failures@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium main branch: 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: clank-library-failures@google.com Merge-Approval-Bypass: Chrome autoroller Change-Id: Ib5221c6b1f3cf12fc2b58dd8be7746dba8abc1f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6832146 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@{#1498728}
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.