Add logging to debug DumpAccessibilityEvent* tests WinClang*

Add logging to debug DumpAccessibilityEvent* tests WinClang*

Note that accessibility_event_recorder_win a test helper, this
doesn't add logging to Chrome.

BUG=440579
NOPRESUBMIT=true

Committed: https://crrev.com/057083929d5871f570909340dfe36564880380f6
Cr-Commit-Position: refs/heads/master@{#313677}

[dmazzoni, 2015-01-28 21:31:25]

dmazzoni@chromium.org changed reviewers:
+ thakis@chromium.org

[Nico, 2015-01-28 22:31:52]

lgtm, thanks

(maybe include a bug link and a TODO to remove all the logging; either in a
comment or in a log message or something)

[Nico, 2015-01-28 22:32:15]

and if you want, you can unswarm this test on CrWinClang tester, then a test
failure will happen sooner

[dmazzoni, 2015-01-28 22:39:25]

dmazzoni@chromium.org changed reviewers:
+ phajdan.jr@chromium.org

[dmazzoni, 2015-01-28 22:39:25]

+phajdan.jr for testing/buildbot

Nico, I'm assuming that's what you had in mind?

[dmazzoni, 2015-01-28 22:39:47]

On 2015/01/28 22:31:52, Nico wrote:
> (maybe include a bug link and a TODO to remove all the logging; either in a
> comment or in a log message or something)

Done

[Nico, 2015-01-29 02:16:54]

https://codereview.chromium.org/873313009/diff/20001/testing/buildbot/chromiu...
File testing/buildbot/chromium.fyi.json (right):

https://codereview.chromium.org/873313009/diff/20001/testing/buildbot/chromiu...
testing/buildbot/chromium.fyi.json:406: },
I would've replaced this whole block with just "content_browsertests". If Pawel
says that just toggling this to false does the same thing, this lgtm as is too.
(Or you could just check it in and we'd find out what happens – I'm kind of
curious :-) )

[dmazzoni, 2015-01-29 07:28:21]

The CQ bit was checked by dmazzoni@chromium.org

[commit-bot: I haz the power, 2015-01-29 07:29:17]

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

[dmazzoni, 2015-01-29 07:29:24]

These tests just flaked on the main waterfall. I'm going to land the change
without the buildbot changes, I think I'll get some info before too long without
messing with the swarming flag.

[commit-bot: I haz the power, 2015-01-29 07:34:56]

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

[commit-bot: I haz the power, 2015-01-29 07:34:57]

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

[dmazzoni, 2015-01-29 08:02:51]

The CQ bit was checked by dmazzoni@chromium.org

[commit-bot: I haz the power, 2015-01-29 08:03:48]

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

[commit-bot: I haz the power, 2015-01-29 08:04:41]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-01-29 08:07:23]

Patchset 3 (id:??) landed as
https://crrev.com/057083929d5871f570909340dfe36564880380f6
Cr-Commit-Position: refs/heads/master@{#313677}