Perf bisect for bug 548009 on behalf of qyearsley@google.com

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': '',
+  "bad_revision": "355747",
+  "bisect_mode": "mean",
+  "bug_id": "548009",
+  "builder_type": "perf",
+  "command": "tools/perf/run_benchmark -v --browser=android-chromium --output-format=buildbot --also-run-disabled-tests smoothness.tough_animation_cases",
+  "good_revision": "355660",
+  "max_time_minutes": "20",
+  "metric": "frame_times/frame_times",
+  "repeat_count": "20",
+  "target_arch": "ia32",
+  "truncate_percent": "25"
 }
 
 # Workaround git try issue, see crbug.com/257689