commit | b0f30e6973f19a15a2d4a43e73e99c34cd9d0b44 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sun May 07 22:58:06 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun May 07 22:58:06 2023 |
tree | 675795c41da07c71a47e2d8433eb7252c9711519 | |
parent | b5facbbd7a459a8b45efbd83d7a091311c456ddc [diff] |
Roll Chrome Win64 PGO Profile Roll Chrome Win64 PGO profile from chrome-win64-main-1683482102-27f9c62b07c99bfb5ba2e04da0f9fe786a7e17d7.profdata to chrome-win64-main-1683493173-3fc5e2e9d5c5a00783acfc7a3d61703254a9e1bd.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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug 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: I498007c8a61e21ad195c0f786123834044e51346 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4510406 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@{#1140657}
diff --git a/chrome/build/win64.pgo.txt b/chrome/build/win64.pgo.txt index a46fb042..baad171 100644 --- a/chrome/build/win64.pgo.txt +++ b/chrome/build/win64.pgo.txt
@@ -1 +1 @@ -chrome-win64-main-1683482102-27f9c62b07c99bfb5ba2e04da0f9fe786a7e17d7.profdata +chrome-win64-main-1683493173-3fc5e2e9d5c5a00783acfc7a3d61703254a9e1bd.profdata