Android: start building libwebview on FYI waterfall.

Android: start building libwebview on FYI waterfall.

Move the libwebview target to android_experimental so it gets compiled
and linked on the FYI waterfall (but not the main waterfall or trybots
yet). This will help us see when it's been broken by other changes.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=151877

[Peter Beverloo, 2012-08-15 12:26:45]

+ilevy

The FYI Builder makes different targets from what we used to run on the FYI
waterfall, so this would be a void change now -- sorry. If it's intentional for
the FYI Builder not to run the experimental tests, we should add the WebView
target to the android_builder_tests section immediately, in which case this
would also be compiled on the main waterfall.

Isaac, can you clarify what the plans are, please? Adding this target would be
comparable to linking content_shell a second time. We have capacity for that
(especially now that we don't re-checkout various git repositories anymore).

https://chromiumcodereview.appspot.com/10829333/diff/1/build/all_android.gyp
File build/all_android.gyp (right):

https://chromiumcodereview.appspot.com/10829333/diff/1/build/all_android.gyp#...
build/all_android.gyp:85:
'../android_webview/lib/android_webview.gyp:libwebview',
It looks like the FYI builder doesn't build the experimental targets anymore,
and unit_tests is duplicated in the normal android_builder_tests section. Isaac,
is this intentional? If so, we should remove this whole block from
all_android.gyp.

[Isaac (away), 2012-08-15 17:21:47]

The compile_experimental is supposed be on the fyi builder.  I didn't add it
initially because we had two fyi builders and the CL to add back
(https://chromiumcodereview.appspot.com/10802033/) got punted.  But I am happy
to land it.

That being said, the builder should not run tests.  How long do you expect the
tests to take?  The right way of doing this is to ensure your target is in the
zip produced by the builder, and run the tests on the fyi testers.`

[Torne, 2012-08-16 09:58:36]

On 2012/08/15 17:21:47, Isaac wrote:
> The compile_experimental is supposed be on the fyi builder.  I didn't add it
> initially because we had two fyi builders and the CL to add back
> (https://chromiumcodereview.appspot.com/10802033/) got punted.  But I am happy
> to land it.
> 
> That being said, the builder should not run tests.  How long do you expect the
> tests to take?  The right way of doing this is to ensure your target is in the
> zip produced by the builder, and run the tests on the fyi testers.`

There's no tests in this target, I just want to check it builds and links.

[Peter Beverloo, 2012-08-16 10:12:07]

This will need a rebase, but LGTM after that. You'll need at least a rubberstamp
from a full committer as well.