Reenable FontRenderParamsTest.Default under Valgrind.

Reenable FontRenderParamsTest.Default under Valgrind.

ui/gfx/ no longer depends on Pango, which was seemingly
causing issues with Fontconfig finalization.

BUG=402209
Committed: https://crrev.com/c4a91a2410df295273464f2ec97d0c4f89c8d3f2
Cr-Commit-Position: refs/heads/master@{#318334}

[Daniel Erat, 2015-02-24 17:12:59]

derat@chromium.org changed reviewers:
+ glider@chromium.org

[Daniel Erat, 2015-02-24 17:12:59]

i don't see any bots that i can use to verify this, but i *think* that this
doesn't crash under valgrind now. here's what i did (for both chromeos=0 and
chromeos=1 linux builds):

- checked out valgrind per
http://www.chromium.org/developers/how-tos/using-valgrind/get-valgrind
- ran "gclient runhooks" with build_for_tool=memcheck
- did a release build of gfx_unittests
- ran "tools/valgrind/chrome_tests.sh --build-dir=out/Release -t gfx"
- saw the following output (some expectations in
PlatformFontLinuxTest.DefaultFont failed on linux, but i think that that's
unrelated and just due to my local font configuration... they passed on chrome
os):

...
09:57:53 common.py [INFO] process ended, did not time out
09:57:53 common.py [INFO] flushing stdout
09:57:53 common.py [INFO] collecting result code
09:57:53 common.py [ERROR]
/derat2/chrome/src/third_party/valgrind/linux_x64/bin/valgrind exited with
non-zero result code 1
-----------------------------------------------------
Suppressions used:
  count name
      3 Fontconfig leak?
      3 glibc-2.5.x-on-SUSE-10.2-(PPC)-2a
-----------------------------------------------------
09:57:53 memcheck_analyze.py [INFO] PASS! No errors found!
09:57:53 valgrind_test.py [ERROR] Test execution failed.
09:57:53 valgrind_test.py [INFO] elapsed time: 00:06:15

[Daniel Erat, 2015-02-26 17:32:45]

derat@chromium.org changed reviewers:
+ thestig@chromium.org

[Lei Zhang, 2015-02-26 21:52:59]

lgtm, let's see what happens.

[Daniel Erat, 2015-02-26 22:01:56]

The CQ bit was checked by derat@chromium.org

[commit-bot: I haz the power, 2015-02-26 22:03:07]

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

[commit-bot: I haz the power, 2015-02-26 22:51:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-26 22:54:39]

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