Doc how to see output from browser in benchmarks
Lack of this knowledge hung me up for several days, and this is one of the places I looked for it. Change-Id: I8da4b1e287da80b24ff61e6cbc2d651a07fda4f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5050987 Reviewed-by: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Dustin Mitchell <djmitche@chromium.org> Cr-Commit-Position: refs/heads/main@{#1227934}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
33d208eaa4
commit
9b9dfe12d2
@ -101,6 +101,11 @@ src$ tools/perf/run_benchmark benchmark_name --story-filter story_name
|
||||
If the run crashes, it is often helpful to add the `-v` flag in order to better
|
||||
understand what is causing the crash.
|
||||
|
||||
If you would like to add logging to the browser to help debug, or if you need to
|
||||
see a stack trace for a crash, use
|
||||
`--extra-browser-args=--enable-logging=stdout` and `--show-stdout` to see that
|
||||
logging.
|
||||
|
||||
### Can I get a trace?
|
||||
|
||||
For most metrics, yes. Here are the steps:
|
||||
|
Reference in New Issue
Block a user