Update documentation for new perf bisect command.

Removed outdated documentation from bisect output, redirected it to chromium.org documentation

BUG=

Committed: https://crrev.com/fd497eb344a16b4297e36f2e1e93e71bbbe767ca
Cr-Commit-Position: refs/heads/master@{#292193}

[sullivan, 2014-08-26 16:28:10]

sullivan@chromium.org changed reviewers:
+ prasadv@chromium.org, tony@chromium.org

[sullivan, 2014-08-26 16:28:10]

I wasn't able to figure out how to get the actual perf trybot name, maybe I
missed something?

[tony, 2014-08-26 16:47:47]

tony@chromium.org changed reviewers:
+ tonyg@chromium.org
- tony@chromium.org

[prasadv, 2014-08-27 16:20:38]

lgtm

[sullivan, 2014-08-27 16:26:49]

The CQ bit was checked by sullivan@chromium.org

[commit-bot: I haz the power, 2014-08-27 16:27:24]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sullivan@chromium.org/507723002/20001

[tonyg, 2014-08-27 16:38:59]

https://codereview.chromium.org/507723002/diff/20001/tools/bisect-perf-regres...
File tools/bisect-perf-regression.py (right):

https://codereview.chromium.org/507723002/diff/20001/tools/bisect-perf-regres...
tools/bisect-perf-regression.py:241: (Where <bot-name> comes from
tools/perf/run_benchmark --browser=list)
I think an important thing to do here is to give them the bot name rather than
asking them to find it. We already know exactly which bot this bisect ran on and
the problem we've had in the past is that authors didn't understand that the
regression was platform specific, thus leading to confusion like in
https://docs.google.com/a/google.com/document/d/1GpQI97nMsye57o6JNLyFSpvzY0fL...

[commit-bot: I haz the power, 2014-08-27 17:47:54]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...)
  android_dbg_tests_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg_tes...)

[commit-bot: I haz the power, 2014-08-27 18:43:30]

Committed patchset #2 (id:20001) as 8138e22c547f394f9666738d1a8a31d368d08d3d

[sullivan, 2014-08-27 22:02:49]

https://codereview.chromium.org/507723002/diff/20001/tools/bisect-perf-regres...
File tools/bisect-perf-regression.py (right):

https://codereview.chromium.org/507723002/diff/20001/tools/bisect-perf-regres...
tools/bisect-perf-regression.py:241: (Where <bot-name> comes from
tools/perf/run_benchmark --browser=list)
On 2014/08/27 16:38:59, tonyg wrote:
> I think an important thing to do here is to give them the bot name rather than
> asking them to find it. We already know exactly which bot this bisect ran on
and
> the problem we've had in the past is that authors didn't understand that the
> regression was platform specific, thus leading to confusion like in
>
https://docs.google.com/a/google.com/document/d/1GpQI97nMsye57o6JNLyFSpvzY0fL...

I'm really sorry this got committed without addressing your comment. Feel free
to revert while I am on vacation.

I agree it would be much better to print the name of the bisect bot. But I
wasn't able to find the name.

There is the function GetBuilderNameAndBuildTime(), but it looks like it returns
the builder, not the tryserver.

There is builder_host, but I think that is an http hostname and not the
buildername, right?

Prasad, Tony, any ideas how I can get the tryserver name, e.g.
mac_10_9_perf_bisect?

[commit-bot: I haz the power, 2014-09-10 02:53:02]

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