Add --accept-crbug-539509 flag to run-webkit-tests

third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/factory.py

Index: third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/factory.py
diff --git a/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/factory.py b/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/factory.py
index 70769d432813a8f2f8244fb4bfdbbbda61ea3edb..38871f606deec70666b9660a4a0a5d8ae37b602c 100644
--- a/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/factory.py
+++ b/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/factory.py
@@ -59,6 +59,8 @@ def configuration_options():
                              help="specify the target configuration to use (Debug/Release)"),
         optparse.make_option('--release', action='store_const', const='Release', dest="configuration",
             help='Set the configuration to Release'),
+        optparse.make_option('--accept-crbug-539509', action='store_true', default=False,
+                             help='Run tests with a non-standard --target despite https://crbug.com/539509'),

[Ken Russell (switch to Gerrit), 2016/02/18 16:41:15]

Rather than add this command line flag, could you help by parsing
out/${target}/args.gn and determine whether the build is Debug or Release from
the flags there? It shouldn't be more than about 10 lines of Python code and
will be the correct fix, rather than adding a broken workaround.

         ]