Disable DelegateGetFontList test on Android through C++.

Disable DelegateGetFontList test on Android through C++.

Instead of disabling it through a file under build/android, better to
disable it directory in C++ source code to avoid sutle issues in the
bots that was caused when renaming the test or the test suite target
name.

BUG=339980
TEST=ui_unittests_apk
R=sky@chromium.org,primiano@chromium.org

Committed: https://crrev.com/4642d9377d3044c81d0f32298ba0c203976c8cc9
Cr-Commit-Position: refs/heads/master@{#297637}

[tfarina, 2014-09-26 19:35:11]

See https://codereview.chromium.org/603413002/ for the findings.

[Primiano Tucci (use gerrit), 2014-09-29 09:25:06]

Not an owner of ui/base but the change LGTM.
Just to double check if I am getting all the story here correctly: the problem
here was that you refactored / renamed the test, and the exclusion rule
(ui_unittests_disabled) was not applying anymore. Hence we ended up running a
test that was not meant to be run on Android.
Does it sound right?

P.S: Small nit in the commit message: "that be caused"

[tfarina, 2014-09-29 13:10:15]

On 2014/09/29 09:25:06, Primiano Tucci wrote:
> Not an owner of ui/base but the change LGTM.
> Just to double check if I am getting all the story here correctly: the problem
> here was that you refactored / renamed the test, and the exclusion rule
> (ui_unittests_disabled) was not applying anymore. Hence we ended up running a
> test that was not meant to be run on Android.
> Does it sound right?
> 
For the ui_base_unittests case, the test DelegateGetFontList went undisabled for
Android because there was no
build/android/pylib/gtest/filter/ui_base_unittests_disabled to disable it.

Same thing can happen if someone come later and rename
ResourceBundleTest.DelegateGetFontList to something else and forget to update
the file under build/android/pylib/gtest/filter/.

> P.S: Small nit in the commit message: "that be caused"
Ops, thanks for catching that! Fixed.

[tfarina, 2014-09-30 20:37:15]

Scott, ping? I need your approval for ui/ to land this.

Thanks,

[sky, 2014-09-30 21:42:50]

LGTM

[tfarina, 2014-10-01 02:15:56]

The CQ bit was checked by tfarina@chromium.org

[commit-bot: I haz the power, 2014-10-01 02:16:35]

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

[commit-bot: I haz the power, 2014-10-01 04:11:03]

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

[commit-bot: I haz the power, 2014-10-01 04:11:04]

Try jobs failed on following builders:
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[tfarina, 2014-10-01 13:06:33]

The CQ bit was checked by tfarina@chromium.org

[commit-bot: I haz the power, 2014-10-01 13:07:14]

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

[commit-bot: I haz the power, 2014-10-01 13:47:48]

Committed patchset #2 (id:20001) as 5f1a78550394a218e4108a7ee90375ea4acf2d7b

[commit-bot: I haz the power, 2014-10-01 13:48:45]

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