Shard & set hard timeout for telemetry_perf_unittests

testing/buildbot/chromium.linux.json

Index: testing/buildbot/chromium.linux.json
diff --git a/testing/buildbot/chromium.linux.json b/testing/buildbot/chromium.linux.json
index f0758b0329f23e009e46ac7ce2d4ccb0492b9451..89790bd3eb1224523ccd0c262eb70cdec767eab5 100644
--- a/testing/buildbot/chromium.linux.json
+++ b/testing/buildbot/chromium.linux.json
@@ -620,7 +620,8 @@
               "device_type": "hammerhead"
             }
           ],
-          "hard_timeout": 1920
+          "hard_timeout": 960,
+          "shards": 12

[jbudorick, 2016/06/23 13:13:55]

What was the motivation here?

This is _really_ problematic for capacity & should likely be backed out.

[nednguyen, 2016/06/23 13:18:28]

Oh, this is just meant to make it consistent with other telemetry configurations
on other platform. Do we have capacity monitoring? I can adjust the number of
tests run to keep it under our budget.

[ghost stip (do not use), 2016/06/23 14:03:58]

we are currently at negative capacity. we need to crank this back to 1 until we
stabilize.

         }
       }
     ],
@@ -1478,7 +1479,9 @@
           "telemetry_perf_unittests_run"
         ],
         "swarming": {
-          "can_use_on_swarming_builders": true
+          "can_use_on_swarming_builders": true,
+          "hard_timeout": 960,
+          "shards": 12
         }
       },
       {
@@ -1897,7 +1900,9 @@
           "telemetry_perf_unittests_run"
         ],
         "swarming": {
-          "can_use_on_swarming_builders": true
+          "can_use_on_swarming_builders": true,
+          "hard_timeout": 960,
+          "shards": 12
         }
       },
       {