Perf bisect for bug 430628 on behalf of None

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 26 matching lines @@
   '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',
 """
 
 config = {
-  'command': '',
-  'good_revision': '',
-  'bad_revision': '',
-  'metric': '',
-  'repeat_count': '',
-  'max_time_minutes': '',
-  'truncate_percent': '',
+  'command': 'python tools/perf/run_benchmark -v --browser=release page_cycler.intl_hi_ru',
+  'good_revision': '302379',
+  'bad_revision': '302380',
+  'metric': 'warm_times/page_load_time',
+  'repeat_count': '10',
+  'max_time_minutes': '20',
+  'truncate_percent': '25',
+  'bug_id': '430628', 
+  'gs_bucket': 'chrome-perf',
+  'builder_host': 'master4.golo.chromium.org',
+  'builder_port': '8341',
 }
 
 # Workaround git try issue, see crbug.com/257689