commit | 6e446a7e4ad81e0109e68c10a5268f5ac508604b | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Aug 13 06:13:59 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 13 06:13:59 2024 |
tree | 67c2ee304c2bb81c537f8d95d676782b72471d1f | |
parent | 45e99bba7e5a95329b8322b3eafa001b26d302a2 [diff] |
Roll Chrome Win32 PGO Profile Roll Chrome Win32 PGO profile from chrome-win32-main-1723507137-8c74908c90d40f3cbadac8f23da24645191d990a-5512728a773aad80e6f8e3f2b8f2923627390043.profdata to chrome-win32-main-1723517604-0edfbde61708eba29d8dedf16d26dc9c966522e7-185dc588dd41acf060b24e7ddbd5ae9210a3a9be.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-win32-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 Cq-Include-Trybots: luci.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I58c74053d34ca316b6a201829be2ad1636cee53b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5785086 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@{#1340813}
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.