Do not filter using analyze step if layout tests are modified.

testing/buildbot/trybot_analyze_config.json

Index: testing/buildbot/trybot_analyze_config.json
diff --git a/testing/buildbot/trybot_analyze_config.json b/testing/buildbot/trybot_analyze_config.json
index a46740814283ecba3956c30ff65f97ff2b92317b..3103028c488cf24156d5e6048ab90346ff2af423 100644
--- a/testing/buildbot/trybot_analyze_config.json
+++ b/testing/buildbot/trybot_analyze_config.json
@@ -25,6 +25,7 @@
       "testing/scripts/.*",
       "testing/test_env.py",
       "third_party/android_platform/development/scripts/.*",
+      "third_party/WebKit/LayoutTests/.*",

[qyearsley, 2016/07/28 23:33:29]

Maybe this should be "third_party/WebKit/.*" -- then the analyze step would be
ignored for all CLs that modify anything in Blink, I believe?

As far as I understand, the purpose of the "analyze" step is to pare down the
list of targets to build (and tests to run) to avoid wasting resources -- so if
this exclusion list is too broad, then the negative effect would be potentially
running some unnecessary tests, but it would never fail to run a test should be
run, right?

[Dirk Pranke, 2016/07/29 23:58:55]

In GN, you can actually set a "data" attribute on a build target, and if
something listed in that target changes, then the target will be considered
affected.

I.e., instead of doing this, you should add `data = [
"//third_party/WebKit/LayoutTests/", "//third_party/WebKit/Tools/Scripts/"]` to
the blink_tests target in //BUILD.gn

       "tools/clang/blink_gc_plugin/CMakeLists.txt",
       "tools/luci-go/.*"
     ]