First pass performance try bot.

tools/run-perf-test.cfg

Index: tools/run-perf-test.cfg
diff --git a/tools/run-bisect-perf-regression.cfg b/tools/run-perf-test.cfg
similarity index 76%
copy from tools/run-bisect-perf-regression.cfg
copy to tools/run-perf-test.cfg
index ded25d259379d921a01ce229c4ac7b72dc77f0d2..a778b65075b4c05f7a16f58b1a43205c57946edf 100644
--- a/tools/run-bisect-perf-regression.cfg
+++ b/tools/run-perf-test.cfg
@@ -2,11 +2,11 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-"""Config file for Run Performance Test Bisect Tool
+"""Config file for Run Performance Test Bot
 
-This script is intended for use by anyone that wants to run a remote bisection
-on a range of revisions to look for a performance regression. Modify the config
-below and add the revision range, performance command, and metric. You can then
+This script is intended for use by anyone that wants to run a remote performance
+test. Modify the config below and add the command to run the performance test,
+the metric you're interested in, and repeat/discard parameters. You can then
 run a git try <bot>.
 
 Changes to this file should never be submitted.
@@ -14,9 +14,6 @@ Changes to this file should never be submitted.
 Args:
   'command': This is the full command line to pass to the
       bisect-perf-regression.py script in order to execute the test.
-  'good_revision': An svn or git revision where the metric hadn't regressed yet.
-  'bad_revision': An svn or git revision sometime after the metric had
-      regressed.
   'metric': The name of the metric to parse out from the results of the
       performance test. You can retrieve the metric by looking at the stdio of
       the performance test. Look for lines of the format:
@@ -34,8 +31,6 @@ Sample config:
 config = {
   'command': './out/Release/performance_ui_tests' +
       ' --gtest_filter=PageCyclerTest.Intl1File',
-  'good_revision': '179755',
-  'bad_revision': '179782',
   'metric': 'times/t',
   'repeat_count': '20',
   'max_time_minutes': '20',
@@ -48,8 +43,6 @@ the command:
 
 config = {
   'command': 'python tools/perf/run_measurement -v --browser=release kraken',
-  'good_revision': '185319',
-  'bad_revision': '185364',
   'metric': 'Total/Total',
   'repeat_count': '20',
   'max_time_minutes': '20',
@@ -66,8 +59,6 @@ config = {
   'command': './tools/perf/run_measurement -v '\
       '--browser=cros-chrome-guest '\
       'dromaeo tools/perf/page_sets/dromaeo/jslibstylejquery.json',
-  'good_revision': '4086.0.0',
-  'bad_revision': '4087.0.0',
   'metric': 'jslib/jslib',
   'repeat_count': '20',
   'max_time_minutes': '20',
@@ -78,12 +69,10 @@ config = {
 
 config = {
   'command': '',
-  'good_revision': '',
-  'bad_revision': '',
   'metric': '',
-  'repeat_count':'',
+  'repeat_count': '',
   'max_time_minutes': '',
-  'truncate_percent':'',
+  'truncate_percent': '',
 }
 
 # Workaround git try issue, see crbug.com/257689