Fix flags for Chromecast browser test on internal infrastructure

Fix flags for Chromecast browser test on internal infrastructure

The media playback test was recently added:
https://codereview.chromium.org/1431193005/

and requires specific switches:
* local file access required to load test media
* cma pipeline explicitly enabled in order to test that
* cast ozone platform enabled in order to test overlay frames

These tests have been failing on internal infrastructure (tot build)
because the switches were only configured in testing/buildbot (for
running on Chromium bots).

BUG=

Committed: https://crrev.com/146527ab5e3cf1f54dc36f4d1d06d7db9cfc913b
Cr-Commit-Position: refs/heads/master@{#361134}

[halliwell, 2015-11-21 02:52:06]

Description was changed from

==========
Fix flags for Chromecast browser test on internal infrastructure

The media playback test was recently added:
https://codereview.chromium.org/1431193005/

and requires specific switches:
* local file access required to load test media
* cma pipeline explicitly enabled in order to test that
* cast ozone platform enabled in order to test overlay frames

These tests have been failing on internal infrastructure (tot build)
because the switches were only configured in testing/buildbot (for
running on Chromium bots).

BUG=
==========

to

==========
Fix flags for Chromecast browser test on internal infrastructure

The media playback test was recently added:
https://codereview.chromium.org/1431193005/

and requires specific switches:
* local file access required to load test media
* cma pipeline explicitly enabled in order to test that
* cast ozone platform enabled in order to test overlay frames

These tests have been failing on internal infrastructure (tot build)
because the switches were only configured in testing/buildbot (for
running on Chromium bots).

BUG=
==========

[halliwell, 2015-11-21 02:52:06]

halliwell@chromium.org changed reviewers:
+ sanfin@chromium.org, slan@chromium.org

[slan, 2015-11-21 02:58:32]

lgtm

https://codereview.chromium.org/1466633004/diff/1/chromecast/BUILD.gn
File chromecast/BUILD.gn (left):

https://codereview.chromium.org/1466633004/diff/1/chromecast/BUILD.gn#oldcode111
chromecast/BUILD.gn:111: filters += [ "cast_shell_browser_test --no-sandbox
--disable-gpu" ]
no --disable-gpu flag is intentional right?

[halliwell, 2015-11-21 03:11:30]

On 2015/11/21 02:58:32, slan wrote:
> lgtm
> 
> https://codereview.chromium.org/1466633004/diff/1/chromecast/BUILD.gn
> File chromecast/BUILD.gn (left):
> 
>
https://codereview.chromium.org/1466633004/diff/1/chromecast/BUILD.gn#oldcode111
> chromecast/BUILD.gn:111: filters += [ "cast_shell_browser_test --no-sandbox
> --disable-gpu" ]
> no --disable-gpu flag is intentional right?

Correct.  Because previously we didn't have ozone-platform=cast, and starting
the GPU process would fail (I actually forget the full details of why).

Now we use ozone-platform=cast, which in turn defers to libcast_graphics for the
underlying platform bindings.  When we run on x86, it's just a complete dummy
implementation, but it's enough for the test to pass.  On our devices, it should
actually display stuff.

And by using our ozone platform, we exercise our overlay system end-to-end.

[halliwell, 2015-11-23 17:11:40]

The CQ bit was checked by halliwell@chromium.org

[commit-bot: I haz the power, 2015-11-23 17:12:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1466633004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1466633004/1

[commit-bot: I haz the power, 2015-11-23 17:47:37]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-23 17:48:35]

Patchset 1 (id:??) landed as
https://crrev.com/146527ab5e3cf1f54dc36f4d1d06d7db9cfc913b
Cr-Commit-Position: refs/heads/master@{#361134}