Adding isolate for cc_perftests and triggering job on FYI waterfall

testing/buildbot/chromium.perf.fyi.json

Index: testing/buildbot/chromium.perf.fyi.json
diff --git a/testing/buildbot/chromium.perf.fyi.json b/testing/buildbot/chromium.perf.fyi.json
index a1e14c59d48f3b3aff1d817622541f8b2cf28f12..6618dc3a827bc422acbee6c079f0bb480a64540f 100644
--- a/testing/buildbot/chromium.perf.fyi.json
+++ b/testing/buildbot/chromium.perf.fyi.json
@@ -4,9 +4,6 @@
   "Android Galaxy S5 Perf (1)": {
     "scripts": [
       {
-        "args": [
-          "cc_perftests"
-        ],
         "name": "cc_perftests",
         "script": "gtest_perf_test.py"
       },
@@ -23,6 +20,34 @@
     "isolated_scripts": [
       {
         "args": [
+          "cc_perftests"
+        ],
+        "isolate_name": "cc_perftests",
+        "name": "cc_perftests",
+        "override_compile_targets": [
+          "cc_perftests"
+        ],

[Dirk Pranke, 2016/10/26 18:55:10]

are all three of these args actually needed? Why isn't "name" sufficient?

[eyaich1, 2016/10/27 14:39:53]

name and isolate_name are needed as the name is the perf id which just happens
to be the same in this instance.  override_compile_targets I believe is just for
gyp so I *think* I can safely remove it.

+        "swarming": {
+          "can_use_on_swarming_builders": true,
+          "dimension_sets": [
+            {
+              "gpu": "8086:22b1",
+              "id": "build187-b4",
+              "os": "Windows-10-10586",
+              "pool": "Chrome-perf"
+            },
+            {
+              "gpu": "1002:9874",
+              "id": "build171-b4",
+              "os": "Windows-10-10586",
+              "pool": "Chrome-perf"
+            }
+          ],
+          "expiration": 14400
+        }
+      },
+      {
+        "args": [
           "dromaeo.cssqueryjquery",
           "-v",
           "--upload-results",