Add more OWNERs to content/public/android

Add more OWNERs to content/public/android

BUG=None
NOTRY=true

Committed: https://crrev.com/680879373111af996eb06886910a58af5c7538ca
Cr-Commit-Position: refs/heads/master@{#314598}

[aurimas (slooooooooow), 2015-02-04 01:10:48]

aurimas@chromium.org changed reviewers:
+ tedchoc@chromium.org, yfriedman@chromium.org

[aurimas (slooooooooow), 2015-02-04 01:10:49]

tedchoc, yfriedman: PTAL.

cc: dtrainor@chromium.org, newt@chromium.org, yusufo@chromium.org,
dfalcantara@chromium.org as they get added to OWNERS

[Ted C, 2015-02-04 16:37:23]

lgtm

[aurimas (slooooooooow), 2015-02-04 17:24:59]

The CQ bit was checked by aurimas@chromium.org

[commit-bot: I haz the power, 2015-02-04 17:25:33]

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

[commit-bot: I haz the power, 2015-02-04 17:54:39]

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

[commit-bot: I haz the power, 2015-02-04 17:54:40]

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

[aurimas (slooooooooow), 2015-02-04 18:19:27]

The CQ bit was checked by aurimas@chromium.org

[commit-bot: I haz the power, 2015-02-04 18:20:56]

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

[commit-bot: I haz the power, 2015-02-04 18:47:54]

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

[commit-bot: I haz the power, 2015-02-04 18:47:55]

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

[aurimas (slooooooooow), 2015-02-04 18:56:00]

The CQ bit was checked by aurimas@chromium.org

[commit-bot: I haz the power, 2015-02-04 18:56:55]

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

[commit-bot: I haz the power, 2015-02-04 19:04:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-04 19:05:21]

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

[boliu, 2015-02-04 19:31:09]

On 2015/02/04 19:05:21, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/680879373111af996eb06886910a58af5c7538ca
> Cr-Commit-Position: refs/heads/master@{#314598}

This is actually breaking android_aosp bot for reasons I cannot fathom..

[boliu, 2015-02-04 19:35:32]

On 2015/02/04 19:31:09, boliu wrote:
> On 2015/02/04 19:05:21, I haz the power (commit-bot) wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/680879373111af996eb06886910a58af5c7538ca
> > Cr-Commit-Position: refs/heads/master@{#314598}
> 
> This is actually breaking android_aosp bot for reasons I cannot fathom..

Bahh, can't even revert with "Revert Patchset"

[newt (away), 2015-02-04 19:52:47]

newt@chromium.org changed reviewers:
+ newt@chromium.org

[newt (away), 2015-02-04 19:52:47]

aapt freaks out because the res directory now contains an unexpected resource
file: OWNERS. You can tell aapt to ignore the OWNERS file using the
--ignore-assets option. E.g.

    aapt package .... --ignore-assets
'!OWNERS:!.svn:!.git:!.ds_store:!*.scc:.*:<dir>_*:!CVS:!thumbs.db:!picasa.ini:!*~'

See AAPT_IGNORE_PATTERN in build_utils.py and the places where
AAPT_IGNORE_PATTERN is used.

[aurimas (slooooooooow), 2015-02-04 20:02:23]

aurimas@chromium.org changed reviewers:
+ torne@chromium.org

[aurimas (slooooooooow), 2015-02-04 20:02:24]

+torne@ who according to boliu@ handles resources in WebView. Can you make a
change to WebView aapt step to ignore OWNERS files?

[jam, 2015-02-04 20:04:32]

for future reference, please don't use TBR again for stuff like this. The bot
was obviously broken, as it failed a few times.

[aurimas (slooooooooow), 2015-02-04 20:07:53]

On 2015/02/04 at 20:04:32, jam wrote:
> for future reference, please don't use TBR again for stuff like this. The bot
was obviously broken, as it failed a few times.

I looked at the bot and saw that compile was failing. I was assuming it was a
bot problem as OWNERS files are just static files that do not compile.

[jam, 2015-02-04 20:13:32]

On 2015/02/04 20:07:53, aurimas wrote:
> On 2015/02/04 at 20:04:32, jam wrote:
> > for future reference, please don't use TBR again for stuff like this. The
bot
> was obviously broken, as it failed a few times.
> 
> I looked at the bot and saw that compile was failing. I was assuming it was a
> bot problem as OWNERS files are just static files that do not compile.

yeah, it's so hard to figure out what each build does in its compile or other
steps. In cases where I see weird breakages like this, I look at other runs of
the bots to know if something is busted. even if the tree is broken because of a
bad commit, waiting for the CQ to retry is the best strategy.