tree 95dee9e11858589edd9f7826b52f35cb8ba0084c
parent 9d6d8a9a910a584456c7dc763747cc22e3c335cf
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> 1715917395 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1715917395 +0000

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-main-1715893178-92b1d114da4ea36a054dbcff6a36985a9c1638d8-01e3ddb87dd4948ea375fb4b575bcda10b0e66fc.profdata to chrome-win32-main-1715903876-2e1f6e98921697780a21cbb44881f598bcb2a259-55d0c66ee8a0d46ba9431250e6c79254969f249f.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: If3683ca5b82e1e1d766a5cfbe7b348faf957dd35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5546747
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@{#1302393}