tree 5143ab7da5fa6379b5106bafa27de1fafe91288e
parent f75ac478e07485f58fa4a8d445500f5d4fbdf6f1
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> 1714283397 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1714283397 +0000

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-main-1714261913-2f7e817dc73dc961161c350b4202b97a7a855ad0-f0e49ce2ca39b6c1c2ce3a9b2f645d44cef86cdc.profdata to chrome-win32-main-1714273159-61f3982761087469ce2de573412f542a75272c06-64f663da341bc651bfbc8fba98ce668ee67fb08d.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: I5284773da4acd85fb8c216073157171595f028b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5491938
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@{#1293448}