Bisect config params should alway be empty.

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 41 matching lines @@
 config = {
   'command': ('./tools/perf/run_measurement -v --browser=cros-chrome-guest '
               'dromaeo.jslibstylejquery')
   'good_revision': '4086.0.0',
   'bad_revision': '4087.0.0',
   'metric': 'jslib/jslib',
 }
 """
 
 config = {
-  'max_time_minutes': '20',
-  'metric': 'Total/Total',
-  'builder_port': '8341',
-  'bug_id': '405188',
-  'repeat_count': '20',
-  'good_revision': '288423',
-  'builder_host': 'master4.golo.chromium.org',
-  'truncate_percent': '25',
-  'command': 'tools/perf/run_benchmark -v --browser=release sunspider',
-  'gs_bucket': 'chrome-perf',
-  'bad_revision': '288447',
+  'command': '',
+  'good_revision': '',
+  'bad_revision': '',
+  'metric': '',
+  'repeat_count': '',
+  'max_time_minutes': '',
+  'truncate_percent': '',
 }
 
 # Workaround git try issue, see crbug.com/257689