Add target for building Chromium tests for WebRTC.

Add target for building Chromium tests for WebRTC.

WebRTC is running the content_browsertests test
for ToT WebRTC revisions to track regressions on an
early stage. In order to save compile time and
build artifacts, we want to build only what's needed
(i.e. not the All target).
In https://codereview.chromium.org/27622005/ an
attempt was made to make content_browsertests_apk
to be enough of target to build (that CL made it also
build android_tools). Since that approach was having
bad sideffects, this helper target should give us
everything needed for our build.

NOTRY=True
TEST=local compile, verifying the apk and host_forwarder is built.
BUG=305749
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=232956

[kjellander_chromium, 2013-10-25 13:41:41]

navabi@: review.

Adding frankf@, cjhopman@ and bulach@ as CC just FYI since they were involved in
analyzing the errors caused by https://codereview.chromium.org/27622005/

[navabi, 2013-10-29 21:04:13]

lgtm

[navabi, 2013-10-29 21:05:30]

On 2013/10/29 21:04:13, navabi wrote:
> lgtm

Best to let someone that analyzed why just building content_browsertests did not
work. I do not know enough about the dependencies for WebRTC tests, but assuming
the dependencies are correct, this lgtm.

[commit-bot: I haz the power, 2013-11-04 09:14:52]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kjellander@chromium.org/43463004/1

[kjellander_chromium, 2013-11-04 09:19:01]

On 2013/10/29 21:05:30, navabi wrote:
> On 2013/10/29 21:04:13, navabi wrote:
> > lgtm
> 
> Best to let someone that analyzed why just building content_browsertests did
not
> work. I do not know enough about the dependencies for WebRTC tests, but
assuming
> the dependencies are correct, this lgtm.

Unfortunately when building just content_browsertests_apk, the android tools are
not built, so forwarder2 is not present, causing test execution to fail. 
There is a discussion in https://codereview.chromium.org/27622005 where I tried
to add the is_test_apk=1 variable to the target to get these things built, which
however turned out to cause other problems and it getting reverted.
Setting up a separate helper GYP target seems to be the best way to resolve
this.

[commit-bot: I haz the power, 2013-11-04 09:31:57]

Retried try job too often on chromium_presubmit for step(s) presubmit
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...

[kjellander_chromium, 2013-11-04 09:37:59]

Armand, can you lgtm with your navabi@chromium.org account? I don't think your
google.com account is good enough for this (according to the chromium_presubmit
trybot result)

[navabi1, 2013-11-04 22:08:24]

On 2013/11/04 09:37:59, Henrik Kjellander wrote:
> Armand, can you lgtm with your mailto:navabi@chromium.org account? I don't
think your
> http://google.com account is good enough for this (according to the
chromium_presubmit
> trybot result)

lgtm

[commit-bot: I haz the power, 2013-11-05 08:06:04]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kjellander@chromium.org/43463004/1

[commit-bot: I haz the power, 2013-11-05 12:03:31]

Retried try job too often on win7_aura for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win7_aura&...

[commit-bot: I haz the power, 2013-11-05 12:09:09]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kjellander@chromium.org/43463004/1

[commit-bot: I haz the power, 2013-11-05 13:34:17]

Change committed as 232956