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/1393545Reviewed-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}

base/logging_unittest.cc

@@ -829,17 +829,10 @@ TEST_F(LoggingTest, LogPrefix) {
   log_string_ptr = nullptr;
 }
 
-// Crashes on Win 10 only.  https://crbug.com/897735
-#if defined(OS_WIN)
-#define MAYBE_LogMessageMarkersOnStack DISABLED_LogMessageMarkersOnStack
-#else
-#define MAYBE_LogMessageMarkersOnStack LogMessageMarkersOnStack
-#endif
-
 #if !defined(ADDRESS_SANITIZER) && !defined(MEMORY_SANITIZER)
 // Since we scan potentially uninitialized portions of the stack, we can't run
 // this test under any sanitizer that checks for uninitialized reads.
-TEST_F(LoggingTest, MAYBE_LogMessageMarkersOnStack) {
+TEST_F(LoggingTest, LogMessageMarkersOnStack) {
   const uint32_t kLogStartMarker = 0xbedead01;
   const uint32_t kLogEndMarker = 0x5050dead;
   const char kTestMessage[] = "Oh noes! I have crashed! 💩";