Refactoring auto-bisect bot

tools/auto_bisect/bisect.cfg

 # Copyright (c) 2013 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 """Config file read by run-bisect-perf-regression.py.
 
 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
 run a git try <bot>.
@@ skipping 23 matching lines @@
   'good_revision': '14ac2486c0eba1266d2da1c52e8759d9c784fe80',
   'bad_revision': 'fcf8643d31301eea990a4c42d7d8c9fc30cc33ec',
   'repeat_count': '20',
   'max_time_minutes': '20',
   'truncate_percent': '25',
 }
 
 For Windows, if you're calling a python script you will need to add "python"
 to the command, so the command would be changed to:
     'python tools/perf/run_benchmark -v --browser=release sunspider',
-
-For ChromeOS:
-  - For good and bad revision, the script may accept either ChromeOS versions
-    or unix timestamps.
-  - You don't need to specify --identity and --remote, they will be added to
-    the command using the bot's BISECT_CROS_IP and BISECT_CROS_BOARD values
-  - Example:
-
-config = {
-  'command': ('./tools/perf/run_benchmark -v --browser=cros-chrome-guest '
-              'smoothness.key_mobile_sites')
-  'good_revision': '4086.0.0',
-  'bad_revision': '4087.0.0',
-  'metric': 'mean_frame_time/mean_frame_time',
-}
 """
 
 config = {
   'command': '',
   'good_revision': '',
   'bad_revision': '',
   'metric': '',
   'repeat_count': '',
   'max_time_minutes': '',
   'truncate_percent': '',
 }
 
 # Workaround git try issue, see crbug.com/257689