wez@, PTAL. Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/24ae0f10a6a03123d48054d6be24922580ea9f20

commit 24ae0f10a6a03123d48054d6be24922580ea9f20
Author: Yi Gu <yigu@chromium.org>
Date: Mon Oct 22 14:29:58 2018

Disable LogMessageMarkerOnStack on Windows

The newly added test LoggingTest.LogMessageMarkersOnStack caused
consistent crash on Win10 Test. Disable it ATM and TBR the owner.

TBR=wez@chromium.org
NOTRY=true

Bug:  897735 
Change-Id: Ic775ac5a5cccbe6c5064407ac17534018561468b
Reviewed-on: https://chromium-review.googlesource.com/c/1293670
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601567}
[modify] https://crrev.com/24ae0f10a6a03123d48054d6be24922580ea9f20/base/logging_unittest.cc

Thanks for disabling the test - will take a look :)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/20cf4ff192d2b68f207503ed8e505f21c3729966

commit 20cf4ff192d2b68f207503ed8e505f21c3729966
Author: Wez <wez@chromium.org>
Date: Wed Jan 02 23:11:51 2019

Re-enable LogMessageMarkerOnStack test on Windows.

This test was disabled on Windows in
https://chromium-review.googlesource.com/c/1293670
because of failures on the Windows Debug bots.

The failure cannot be reproduced locally, and we don't have links to
logs from the failed runs, so re-enabling the test to allow us to repro
and diagnose the issue.

Bug:  897735 , 802393
Change-Id: I9086366e7b1f9240674f3b5678810d221b5d01ff
Reviewed-on: https://chromium-review.googlesource.com/c/1393545
Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#619528}
[modify] https://crrev.com/20cf4ff192d2b68f207503ed8e505f21c3729966/base/logging_unittest.cc