Add CT isolate file and CT script that will be run on swarming slaves

chrome/ct_top1k.isolate

+# Copyright (c) 2015 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+{
+  'includes': [
+    # TODO(rmistry): Try out the below once things are running on the
+    #                FYI waterfall.
+    # '../tools/telemetry/telemetry.isolate',
+    # '../tools/perf/perf.isolate',
+    '../tools/perf/chrome_telemetry_build/telemetry_binary_manager.isolate',
+  ],
+  'conditions': [
+    ['OS=="android" or OS=="linux" or OS=="mac" or OS=="win"', {
+      'variables': {
+        'files': [
+          '../build/android/pylib/',
+          '../build/android/devil/',
+          '../testing/variations/',
+          '../third_party/catapult/',
+          '../tools/telemetry/',
+          '../tools/perf/',
+          '../tools/variations/',
+          '../testing/test_env.py',
+          '../out/Release/',

[M-A Ruel, 2015/11/17 18:31:49]

FTR, we generally use <(PRODUCT_DIR), otherwise you defacto do not support
Release_x64 on Windows and Debug.

[rmistry, 2015/11/17 18:33:57]

Do I have to explicitly set PRODUCT_DIR with path_variables (or is it magically
set somewhere)?

[M-A Ruel, 2015/11/17 18:36:16]

No you have to set it, so for now hardcoding this path here is fine and this can
be fixed later.

+
+          '../content/test/ct/run_ct_top1k.py',
+          '../content/test/ct/slave<(SLAVE_NUM)/page_sets/',
+          '../content/test/ct/run_chromium_perf_swarming',
+        ],
+        'command': [
+          'python',
+          '../content/test/ct/run_ct_top1k.py',
+          '--slave_num=<(SLAVE_NUM)',
+          '--benchmark=<(BENCHMARK)',
+          '--master=<(MASTER)',
+          '--builder=<(BUILDER)',
+          '--git_hash=<(GIT_HASH)',
+        ],
+      },
+    }],
+  ]
+}