tree ee4dc6926c4a4949c8038c0f900ca4062ba2f1ed
parent c873d2c93fe4195fd2a1fed7726eb32058a37f82
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> 1741362074 -0800
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1741362074 -0800

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-main-1741316299-23a198c7604c63a69c17d001c4c726a867eedbed-cc50c5a3f4f70e23c7ff534acf28dac549955775.profdata to chrome-win64-main-1741337995-d35a06955eaa68c69457cceea5ca08b2ddc2f018-19f9fabd1f4e166c9dde6e4a834afeac6aabe5b4.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: I55ef1066a60c20f16a1a253c91c8793ca5772e0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6334727
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@{#1429498}