| commit | bc39d1623c203110bb7e10e6ab5b05ae0851abef | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <[email protected]> | Sun Dec 14 03:58:12 2025 |
| committer | Chromium LUCI CQ <[email protected]> | Sun Dec 14 03:58:12 2025 |
| tree | e0d16474ce5cd10e4bf1ccec704fd916881439f7 | |
| parent | 528353beb9a02af866392be6aa578d16e4de23a4 [diff] |
Roll ChromeOS Arm AFDO profile from 145-7559.4-1765165096-benchmark-145.0.7575.0_pre1557201-r1 to 145-7559.4-1765165096-benchmark-145.0.7576.0_pre1557818-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-arm-chromium Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Main: 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: [email protected] Merge-Approval-Bypass: Chrome autoroller Change-Id: I5ac0ab63388e60c12dfae63e19bad408b63d59cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7258139 Bot-Commit: chromium-autoroll <[email protected]> Commit-Queue: chromium-autoroll <[email protected]> Cr-Commit-Position: refs/heads/main@{#1558480}
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.