Index: tools/auto_bisect/configs/linux.bisect.functional.cfg |
diff --git a/tools/auto_bisect/configs/linux.bisect.functional.cfg b/tools/auto_bisect/configs/linux.bisect.functional.cfg |
new file mode 100644 |
index 0000000000000000000000000000000000000000..d5c36991c761d5cdb0fbb82b9438c3c843423bbb |
--- /dev/null |
+++ b/tools/auto_bisect/configs/linux.bisect.functional.cfg |
@@ -0,0 +1,13 @@ |
+# 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': 'out/Release/content_unittests --single-process-tests --gtest_filter=DOMStorageAreaTest', |
+ 'good_revision': '311607', |
+ 'bad_revision': '311608', |
+ 'bisect_mode': 'return_code', |
+ 'builder_type': 'full', |
+} |
+ |
+# Workaround git try issue, see crbug.com/257689 |