tree 84516102138b3284f4cb74434762857085ad0f0e
parent e2401d284b4c01841bc0b52ca75a2896b1a5dbca
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> 1739920487 -0800
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1739920487 -0800

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-main-1739869112-9ed4d35322a0f030f5a75e9743b8592b70e6a173-39e07ed02eaf1e0a4266858d845c9365f7d61dd2.profdata to chrome-win64-main-1739890722-5349423d56a2d0e8f0dc2364a119d220c2f98517-d938382bf5e8e17501bd8ad17f999e3bb32e77b4.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
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I2dc4c4df4e451edc218dde99646c0097c1ff706c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6278490
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@{#1421671}