Disable telemetry tests for Mac 10.9.

Disable telemetry tests for Mac 10.9.

The telemetry tests are failing consistently on OSX 10.9.

BUG=420615
R=tonyg@chromium.org

Committed: https://crrev.com/5503de1eeae0437c1f8160d69b04d6241bc5e974
Cr-Commit-Position: refs/heads/master@{#303114}

[garykac, 2014-11-06 00:01:54]

garykac@chromium.org changed reviewers:
+ phajdan.jr@chromium.org

[garykac, 2014-11-06 00:01:55]

These tests are consistently failing on the Mac 10.9 bots, but I'm not sure
about the best way to disable them.

Another option would be to simply delete the tests from the JSON completely.
However, it's nice to include a reference to the tracking bug, so I'm adding
'_disabled' to the keys to see if that works.

If we have a convention for disabled tests, please let me know. I looked at the
other JSON files and didn't find anything.

[Paweł Hajdan Jr., 2014-11-06 10:40:46]

phajdan.jr@chromium.org changed reviewers:
+ tonyg@chromium.org

[Paweł Hajdan Jr., 2014-11-06 10:40:47]

+Tony FYI

https://codereview.chromium.org/706703003/diff/1/testing/buildbot/chromium.ma...
File testing/buildbot/chromium.mac.json (right):

https://codereview.chromium.org/706703003/diff/1/testing/buildbot/chromium.ma...
testing/buildbot/chromium.mac.json:283: "name_disabled": "telemetry_unittests",
Please don't invent syntax like this - even if it happens to work (not sure
about that) it's just not supported.

We may have to just remove these entries.

[garykac, 2014-11-06 18:33:19]

On 2014/11/06 10:40:47, Paweł Hajdan Jr. wrote:
> We may have to just remove these entries.

Done.

[tonyg, 2014-11-06 22:24:13]

The CQ bit was checked by tonyg@chromium.org

[tonyg, 2014-11-06 22:24:14]

lgtm

[commit-bot: I haz the power, 2014-11-06 22:25:13]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/706703003/20001

[commit-bot: I haz the power, 2014-11-06 22:31:36]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-11-06 22:31:38]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[commit-bot: I haz the power, 2014-11-06 23:03:53]

Patchset 2 (id:??) landed as
https://crrev.com/5503de1eeae0437c1f8160d69b04d6241bc5e974
Cr-Commit-Position: refs/heads/master@{#303114}

[garykac, 2014-11-06 23:03:54]

Committed patchset #2 (id:20001) manually as
5503de1eeae0437c1f8160d69b04d6241bc5e974.

[dtu, 2014-11-11 20:21:07]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/718783002/ by dtu@chromium.org.

The reason for reverting is: Re-enabling these tests. Hopefully this was fixed
by https://codereview.chromium.org/703203004.

[dtu, 2014-11-20 22:48:33]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/744283002/ by dtu@chromium.org.

The reason for reverting is: Second attempt to re-enable tests. I think there
may still be one test failure, but we can disable that one test. If there's more
than one, revert this..