commit | c1b8470a0a73213a99f06e6837d14f46857b5c0a | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sat Mar 08 23:29:49 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Mar 08 23:29:49 2025 |
tree | eeb88146f9fdccb7d16e866bf149d60b69c6ef0e | |
parent | e77d086e894f687671e5ef6b5ea716c5b94f317d [diff] |
Roll Chrome Win32 PGO Profile Roll Chrome Win32 PGO profile from chrome-win32-main-1741445754-684619b7a11c9648975d07b5e17eac9afe95a0d3-928f952a66cabb961d49d4385136020cdce02585.profdata to chrome-win32-main-1741455437-e2291dcd63332b24c551f45619b838fe2e4c38a9-fad0f6a9b16ebc1662222c2c23d32ec05db3211c.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 Merge-Approval-Bypass: Chrome autoroller Change-Id: I94737ea3173ed4887c6e5df9327c1d7db2e1e2aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6338065 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@{#1429950}
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.