| commit | ec4c08bbe4daaee7ed87c4c32784b5cf7caa75e8 | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Aug 28 07:30:48 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 28 07:30:48 2025 |
| tree | b1d9dfc053864d6530463ecba98f42adddb79b34 | |
| parent | 747e8c8f36453eb7cf97a55f53a5937121365208 [diff] |
Roll Chrome Android ARM64 Orderfile from vUHd1lAmD752DuPZM... to b8f10sJTw1WQ-Jfd7... 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: I3ceae36c237f661cef97e652ac2afc8b64e77f75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6894396 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@{#1507562}
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.