Work-around to make webkit test suite work with optdebug==2.

Work-around to make webkit test suite work with optdebug==2.

The test driver doesn't know at the moment if optdebug 1 or 2 has been used (the first is used on the bots, the second
locally in quickcheck). It can't know therefore if slow
asserts can be enabled or not. Trying to enable them leads
to a warning if they weren't compiled, which causes webkit
1:1 text comparison to fail.

Committed: https://crrev.com/096e1972cd4f2b44130f51d4efe4b3a7b3c4f56f
Cr-Commit-Position: refs/heads/master@{#25921}

[Michael Achenbach, 2014-12-22 10:04:13]

machenbach@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Michael Achenbach, 2014-12-22 10:06:51]

PTAL

[Benedikt Meurer, 2014-12-22 10:07:48]

Urghs...LGTM

[Michael Achenbach, 2014-12-22 10:45:55]

The CQ bit was checked by machenbach@chromium.org

[commit-bot: I haz the power, 2014-12-22 10:46:12]

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

[commit-bot: I haz the power, 2014-12-22 11:13:08]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-12-22 11:13:19]

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