commit | 6ac89e00fda2c31e3e7b5fcc26f3928aedf18cc6 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Dec 05 11:40:25 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 05 11:40:25 2023 |
tree | 141ed5f1a879781bbf54bc5f084f7a29bffb0339 | |
parent | c9be27a0ac54c492d3c2a9abb31828e39f8ca013 [diff] |
Roll Chrome Win32 PGO Profile Roll Chrome Win32 PGO profile from chrome-win32-main-1701734389-057db56c69f3a9f26fb623134d6164b8c10723f0.profdata to chrome-win32-main-1701745052-8327d3432d3a568e3ed574cb0d31fb9aece8e98e.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: I53148edae16b15469e3d79c46b5cd80f94293188 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5085592 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@{#1233261}
diff --git a/chrome/build/win32.pgo.txt b/chrome/build/win32.pgo.txt index babc6877..ab55e4f 100644 --- a/chrome/build/win32.pgo.txt +++ b/chrome/build/win32.pgo.txt
@@ -1 +1 @@ -chrome-win32-main-1701734389-057db56c69f3a9f26fb623134d6164b8c10723f0.profdata +chrome-win32-main-1701745052-8327d3432d3a568e3ed574cb0d31fb9aece8e98e.profdata