BattOr.BattOrCases should collect a Chrome trace alongside the BattOr trace |
||
Issue descriptionRight now, the BattOr.BattOrCases benchmark only collects a BattOr trace. We should change that so that it also collects a Chrome trace with the default categories enabled.
,
Jun 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c517fbe6e5a8c78163947583644a6dd3613b1906 commit c517fbe6e5a8c78163947583644a6dd3613b1906 Author: charliea <charliea@chromium.org> Date: Fri Jun 10 22:51:21 2016 [battor benchmark] Enable Chrome tracing in the BattOr benchmark This wasn't possible before due to https://github.com/catapult-project/catapult/issues/2341. BUG= 618370 Review-Url: https://codereview.chromium.org/2051933002 Cr-Commit-Position: refs/heads/master@{#399307} [modify] https://crrev.com/c517fbe6e5a8c78163947583644a6dd3613b1906/tools/perf/benchmarks/battor.py
,
Jun 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c517fbe6e5a8c78163947583644a6dd3613b1906 commit c517fbe6e5a8c78163947583644a6dd3613b1906 Author: charliea <charliea@chromium.org> Date: Fri Jun 10 22:51:21 2016 [battor benchmark] Enable Chrome tracing in the BattOr benchmark This wasn't possible before due to https://github.com/catapult-project/catapult/issues/2341. BUG= 618370 Review-Url: https://codereview.chromium.org/2051933002 Cr-Commit-Position: refs/heads/master@{#399307} [modify] https://crrev.com/c517fbe6e5a8c78163947583644a6dd3613b1906/tools/perf/benchmarks/battor.py
,
Jun 28 2016
(Fixed, along with some work from rnephew@) |
||
►
Sign in to add a comment |
||
Comment 1 by nedngu...@google.com
, Jun 8 2016