commit | 48889ebfba26dc57e6323b7afbfefc0c6436e316 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Oct 22 18:34:18 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 22 18:34:18 2020 |
tree | 920eac95bb775cd7bddaa5432c8d18b7cf86b9cb | |
parent | c0d46895f2e5ef535895b95124c8cf60c2a24576 [diff] |
Roll Chrome Win64 PGO Profile Roll Chrome Win64 PGO profile from chrome-win64-master-1603335567-5b7ae75a80b56b2c3e08e562ca96c9be42987f9c.profdata to chrome-win64-master-1603357187-4783767f29971847246b39ba5f03512056047f0d.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 pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. 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/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I67a2da59d10ad62e66cfefda53219350989e2901 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491809 Reviewed-by: 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/master@{#819909}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.