Clean up logging for debugging RAF related flakiness in WebGL conformance tests.

Clean up logging for debugging RAF related flakiness in WebGL conformance tests.

We figured out which part caused the problom, so these logs are no longer needed.

BUG=393331
TEST=bots
TBR=kbr@chromium.org

Committed: https://crrev.com/006c99bdb5c9940a8263acd77be93f93e5727b28
Cr-Commit-Position: refs/heads/master@{#294937}

[Zhenyao Mo, 2014-09-15 19:53:09]

The CQ bit was checked by zmo@chromium.org

[commit-bot: I haz the power, 2014-09-15 20:05:33]

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

[commit-bot: I haz the power, 2014-09-15 20:22:03]

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

[commit-bot: I haz the power, 2014-09-15 20:22:05]

Try jobs failed on following builders:
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/56113)
  android_arm64_dbg_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_arm64_d...)
  android_chromium_gn_compile_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...)
  mac_chromium_compile_dbg on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[Zhenyao Mo, 2014-09-15 22:11:42]

The CQ bit was checked by zmo@chromium.org

[commit-bot: I haz the power, 2014-09-15 22:39:35]

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

[commit-bot: I haz the power, 2014-09-16 00:17:24]

Committed patchset #1 (id:1) as a7db99c312d7ee793d98082a93aa2efed38f2868

[commit-bot: I haz the power, 2014-09-16 00:20:58]

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

[Ken Russell (switch to Gerrit), 2014-09-16 01:06:22]

LGTM, though I wonder if we should have just turned off the logging in the GPU
recipe for the next time an issue in this area crops up. (Not sure whether these
logs had any run-time cost in Release builds -- can't imagine they would.)

[danakj, 2014-09-16 01:09:51]

On Mon, Sep 15, 2014 at 9:06 PM, <kbr@chromium.org> wrote:

> LGTM, though I wonder if we should have just turned off the logging in the
> GPU
> recipe for the next time an issue in this area crops up. (Not sure whether
> these
> logs had any run-time cost in Release builds -- can't imagine they would.)
>
They're strings that cost us binary size. We should remove them or put them
inside DEBUG only macros.


>
>
> https://codereview.chromium.org/551803006/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.