Index: tools/auto_bisect/configs/linux.bisect.page_cycler.cfg |
diff --git a/tools/auto_bisect/configs/linux.bisect.page_cycler.cfg b/tools/auto_bisect/configs/linux.bisect.page_cycler.cfg |
new file mode 100644 |
index 0000000000000000000000000000000000000000..6f23d448baa214ef2d4238484eacd6bee529fd4d |
--- /dev/null |
+++ b/tools/auto_bisect/configs/linux.bisect.page_cycler.cfg |
@@ -0,0 +1,19 @@ |
+# This should reproduce the regression in http://crbug.com/425582. |
+# It was based on: |
+# http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/704 |
+ |
+config = { |
+ 'command': 'tools/perf/run_benchmark -v --browser=release page_cycler.intl_ar_fa_he', |
+ 'good_revision': '300138', |
+ 'bad_revision': '300148', |
+ 'metric': 'warm_times/page_load_time', |
+ 'repeat_count': '2', |
+ 'max_time_minutes': '5', |
+ 'truncate_percent': '25', |
+ 'bug_id': '425582', |
+ 'gs_bucket': 'chrome-perf', |
+ 'builder_host': 'master4.golo.chromium.org', |
+ 'builder_port': '8341', |
+} |
+ |
+# Workaround git try issue, see crbug.com/257689 |