chromium/src
0
Fork 0
Code Activity

pgo docs: Document what to do on GCS access issues

Browse Source 
Change-Id: I56ca7921ce5555034d7a01e0063d30ffa9da90bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3355018
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/main@{#953858}
This commit is contained in:
Nico Weber
2021-12-23 16:14:12 +00:00
committed by Chromium LUCI CQ
parent 24249ff417
commit 98b74eb966
1 changed files with 4 additions and 0 deletions

4
docs/pgo.md

@ -23,6 +23,10 @@ To produce an executable built with a custom PGO profile:
* `vpython tools/perf/run_benchmark speedometer2 --assert-gpu-compositing --browser=exact --browser-executable=out/path/to/chrome`
* This will produce `*.profraw` files in the current working directory
If this fails with `ServiceException: 401 Anonymous caller does not have storage.objects.get
access to the Google Cloud Storage object.`, then run `download_from_google_storage --config`
(with your @google address; enter 0 as project-id).
* Merge the profiling data
* Get the `llvm-profdata` tool by adding `"checkout_clang_coverage_tools": True,` to `custom_vars` in the gclient config and running `gclient runhooks`.