Adding isolate script targets for all remaining C++ perf tests.

chrome/test/BUILD.gn

Index: chrome/test/BUILD.gn
diff --git a/chrome/test/BUILD.gn b/chrome/test/BUILD.gn
index 54bb2285e3658ee2ad0f0b5cc16ae22c2ef77feb..1e6ae97f6aa67cad3987c48c2317c9d691d1891a 100644
--- a/chrome/test/BUILD.gn
+++ b/chrome/test/BUILD.gn
@@ -2917,6 +2917,14 @@ if (!is_android) {
       ]
     }
 
+    data = [
+      # Needed for isolate script to execute.
+      "//testing/scripts/common.py",
+      "//testing/xvfb.py",
+      "//testing/scripts/run_gtest_perf_test.py",
+      "//tools/perf/generate_legacy_perf_dashboard_json.py",
+    ]
+
     # This target should not require the Chrome executable to run.
     assert_no_deps = [ "//chrome" ]
   }
@@ -2959,6 +2967,21 @@ group("telemetry_perf_tests") {
   ]
 }
 
+group("angle_perftests") {
+  testonly = true
+  data_deps = [
+    "//third_party/angle/src/tests:angle_perftests",
+  ]
+
+  data = [
+    # Needed for isolate script to execute.
+    "//testing/scripts/common.py",
+    "//testing/xvfb.py",
+    "//testing/scripts/run_gtest_perf_test.py",
+    "//tools/perf/generate_legacy_perf_dashboard_json.py",
+  ]

[Dirk Pranke, 2016/11/10 00:26:18]

We should create a common target or targets in //testing for these files and
just depend on that, I think.

[eyaich1, 2016/11/10 15:11:27]

Since this references something in tools/perf we can't put it in testing, so I
am not sure what a common place for this to live would be besides here where the
gn_isolate_map.py can easily reference it.  

I think we could create a group in this file that clumps them once, similar to
what was started in https://codereview.chromium.org/2456793003/ but never
checked in.  I think that is our best bet.

+}

[Dirk Pranke, 2016/11/10 00:26:18]

Later, in a separate patch, can we move these targets out of //chrome/test and
closer to the targets that we're actually testing? There's no need (or really,
reason) for these to live here.

[eyaich1, 2016/11/10 15:11:27]

The problem is angle_perftests lives in third_party and we wouldn't be able to
reference the //testing and //tools targets, so we have to aggregate that
somewhere.

+
 js2gtest("unit_tests_js") {
   test_type = "unit"
   sources = [
@@ -4973,6 +4996,14 @@ if (!is_android && !is_ios && !is_chromecast) {
       "//testing/perf",
     ]
 
+    data = [
+      # Needed for isolate script to execute.
+      "//testing/scripts/common.py",
+      "//testing/xvfb.py",
+      "//testing/scripts/run_gtest_perf_test.py",
+      "//tools/perf/generate_legacy_perf_dashboard_json.py",
+    ]
+
     if (is_win) {
       configs -= [ "//build/config/win:default_incremental_linking" ]
       configs +=