commit | 27b543d96eac40a77789bdada14306867f7d149b | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sat May 18 12:45:18 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat May 18 12:45:18 2024 |
tree | c969ae0f7ce7a8f576b13a65b40923546a168524 | |
parent | 59c96d372dbf0ef01d3878907a1d03eb55c7b007 [diff] |
Roll Chrome Android ARM32 PGO Profile Roll Chrome Android ARM32 PGO profile from chrome-android32-main-1716011846-c0b8d9a373727ba6ea4501bcc289732021d0c429-ade34032a0dce767637e8cfa9b398680bbbad9dc.profdata to chrome-android32-main-1716029083-e964b50d28c336131013165a6fa4a39c7d7fc981-934769e8639a4d3ad694cbd0dd76a1bd9c7c1553.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-android-arm32-chromium Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@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: pgo-profile-sheriffs@google.com Change-Id: I5b03a46ed77a25e1b49210e065043eaef7e7cd36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5545096 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1303023}
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.