Disable chromium_builder_tests entries for chromecast.

Disable chromium_builder_tests entries for chromecast.

R=thakis@chromium.org
BUG=472150
Committed: https://crrev.com/ab581451d0bd05433afeb7e953bb1fcf229915bb
Cr-Commit-Position: refs/heads/master@{#323072}

[Nico, 2015-03-31 16:27:19]

lgtm

https://codereview.chromium.org/1043233002/diff/1/build/all.gyp
File build/all.gyp (right):

https://codereview.chromium.org/1043233002/diff/1/build/all.gyp#newcode423
build/all.gyp:423: ['test_isolation_mode != "noop" and chromecast==0', {
Does chromecast not support running tests on swarming? If not, is there a
tracking bug for that?

[gunsch, 2015-03-31 16:34:41]

https://codereview.chromium.org/1043233002/diff/1/build/all.gyp
File build/all.gyp (right):

https://codereview.chromium.org/1043233002/diff/1/build/all.gyp#newcode423
build/all.gyp:423: ['test_isolation_mode != "noop" and chromecast==0', {
On 2015/03/31 16:27:19, Nico wrote:
> Does chromecast not support running tests on swarming? If not, is there a
> tracking bug for that?

chromium_swarm_tests shouldn't be the issue---but most of those tests are from
chrome.gyp and don't build for us (which is somewhat expected). Removed this
condition and conditioned those out in chromium_swarm_tests itself.

[Nico, 2015-03-31 16:40:11]

lgtm!

[gunsch, 2015-03-31 16:42:29]

The CQ bit was checked by gunsch@chromium.org

[commit-bot: I haz the power, 2015-03-31 16:42:53]

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

[commit-bot: I haz the power, 2015-03-31 18:24:06]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-03-31 18:24:41]

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

[gunsch, 2015-04-01 15:43:41]

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

The reason for reverting is: Chromecast doesn't actually need to build
chromium_builder_tests, so reverting to remove the introduced complexity.

Fixed more correctly in: https://codereview.chromium.org/1049333002/ .