tree dec553977e1949e34c6b15b3524b55c49db18d8b
parent b5bdbbf16bcbd656dfacaeb0684bb9e7dd8a5a4b
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> 1732814655 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1732814655 +0000

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-main-1732783930-6e42c27de369a856c27deeb8c322c3ef13f1acff-9df64a975a05e623c6f53e2e2a1936226b8dc42e.profdata to chrome-win64-main-1732795029-cf57026b877d6570150aa2e061545ef597f7231c-3f81fc0042bf1b0f23e8a71d5e384ffa42933e51.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-win64-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:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I08ad63639eee2a76706297022e8b2341173ad7ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6058110
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@{#1389475}