commit | 3f87850892eb0957fe844842ea71920fddcc07e6 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sat Jun 01 10:39:56 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jun 01 10:39:56 2024 |
tree | fd602bbd24932c70a6e04850de111603860e25bd | |
parent | e0a75c29deb9ae3bbb4ee40a568c12e9ccdd1e50 [diff] |
Roll Chrome Mac Arm PGO Profile Roll Chrome Mac Arm PGO profile from chrome-mac-arm-6478-1717224626-7ef15ea5aff0a9f53f566d1004440c96206abd37-1eefd6b8b5074751e55157376e61fe418fd0f378.profdata to chrome-mac-arm-6478-1717234219-28e2cd7b5af9edee2fe0b4507911c7e0a9f257db-dc7196bbd903a2ee5617a6b2a3ed83b401535f52.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-mac-arm-chromium-beta 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 beta 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: If7748f6d0b7038c03a39c38848c70f4f66e817ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5590634 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/branch-heads/6478@{#982} Cr-Branched-From: e6143acc03189c5e52959545b110d6d17ecd5286-refs/heads/main@{#1300313}
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.