Simplifying repro instructions from bisect output for non telemetry cases.

Simplifying repro instructions from bisect output for non telemetry cases.

- Removed redundant output of the test command.
- Reduced the number of steps to three and wrote them as succintly as
  possible.
- Added the clarifying notes separately at the end.
BUG=404088
Committed: https://crrev.com/39b6931a068a09a41865f1cb43589eb84136da78
Cr-Commit-Position: refs/heads/master@{#296483}

[RobertoCN, 2014-09-23 22:50:50]

robertocn@chromium.org changed reviewers:
+ prasadv@chromium.org, qyearsley@chromium.org

[qyearsley, 2014-09-24 03:03:04]

LGTM with a couple minor suggestions. I'm also in favor of removing more of the
instructions but I think it's also fine as-is.

https://codereview.chromium.org/596963002/diff/1/tools/bisect-perf-regression.py
File tools/bisect-perf-regression.py (right):

https://codereview.chromium.org/596963002/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:215: - Use Test Command given under BISECT JOB
RESULTS above.
What do you think about tweaking this a bit to 'Use the test command given under
the "BISECT JOB RESULTS" section above.' ? (no capitals for Test Command)

I'm fine with it either way, this is just a suggestion.

https://codereview.chromium.org/596963002/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:216: - Consider using a profiler (pass
--profiler=list to list the available ones).
Possible suggestion: You can use a profiler; pass --profiler=list to list
available profilers."

Or, to be less verbose, we could also no mention this here; instead we could in
this section just say:

To run locally, use the test command given under BISECT JOB RESULTS above.

https://codereview.chromium.org/596963002/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:223: 3. Send to the try server: $ git cl try -m
tryserver.chromium.perf -b <bot>
git cl upload and git cl try is actually not necessary now -- it can be done
with 'git try --svn_repo="svn://svn.chromium.org/chrome-try/try-perf" -b <bot>'

(Note, I just put my notes for this in
https://sites.google.com/a/google.com/chromeperf/auto-bisect/hacking-on-auto-...;
we could also put it somewhere else.)

[robertocn1, 2014-09-24 18:15:42]

The CQ bit was checked by robertocn@google.com

[robertocn1, 2014-09-24 18:15:45]

The CQ bit was unchecked by robertocn@google.com

[RobertoCN, 2014-09-24 18:16:23]

The CQ bit was checked by robertocn@chromium.org

[commit-bot: I haz the power, 2014-09-24 18:17:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/596963002/20001

[commit-bot: I haz the power, 2014-09-24 19:15:44]

Committed patchset #2 (id:20001) as 93e7a40a627b791e90a56a6fa67e4e7abb028831

[commit-bot: I haz the power, 2014-09-24 19:17:09]

Patchset 2 (id:??) landed as
https://crrev.com/39b6931a068a09a41865f1cb43589eb84136da78
Cr-Commit-Position: refs/heads/master@{#296483}