Enable telemetry_unittests on chromium.android:Marshmallow 64-bit Tester

testing/buildbot/chromium.android.json

Index: testing/buildbot/chromium.android.json
diff --git a/testing/buildbot/chromium.android.json b/testing/buildbot/chromium.android.json
index 0e013c71d70ecca524662dd0f8b379c8d5c8f1cb..86ed3c166959b07446ab49ed278b7572ca5a08ea 100644
--- a/testing/buildbot/chromium.android.json
+++ b/testing/buildbot/chromium.android.json
@@ -3807,6 +3807,31 @@
         },
         "test": "vr_shell_unittests"
       }
+    ],
+    "isolated_scripts": [
+      {
+        "args": [
+          "--browser=android-chromium",
+          "--device=android"
+        ],
+        "isolate_name": "telemetry_unittests",
+        "name": "telemetry_unittests",
+        "override_compile_targets": [

[jbudorick, 2017/04/14 16:12:55]

optional nit: I don't think this is necessary any more, and I'm working on
pulling these out of our configurations. If you'd like to keep it in for now for
consistency, though, I'm ok with it.

[nednguyen, 2017/04/14 16:16:06]

Yeah, if we remove these, I prefer doing that in a mass refactoring CL to keep
the configs consistent.

+          "telemetry_unittests_run"
+        ],
+        "swarming": {
+          "can_use_on_swarming_builders": true,
+          "dimension_sets": [
+            {
+              "android_devices": "6",
+              "device_os": "MMB29Q",
+              "device_type": "bullhead"
+            }
+          ],
+          "hard_timeout": 960,

[nednguyen, 2017/04/14 16:10:21]

this is 16 minutes, whereas the usual runtime of this on catapult CQ is 8
minutes 30s

+          "shards": 1
+        }
+      }
     ]
   },
   "Marshmallow Tablet Tester": {