Stop cctest/test-log/LogMaps from flaking on Windows.

This patch disables the conditions that cause the test to flake, but
as a band-aid that doesn't fix the underlying issue.

Bug: v8:8084
Change-Id: I46380d0ce4f450c176583330ed760bc3b57b9edc
Reviewed-on: https://chromium-review.googlesource.com/1189822Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#55426}

test/cctest/test-log.cc

@@ -155,12 +155,16 @@ class ScopedLoggerInitializer {
       start = IndexOfLine({search_term}, start);
       if (start == std::string::npos) break;
       std::vector<std::string> columns = Split(log_.at(start), ',');
-      CHECK_LT(address_column, columns.size());
+      ++start;  // Skip the found line.
+      // TODO(crbug.com/v8/8084): These two continue lines should really be
+      // errors. But on Windows the log is sometimes mysteriously cut off at the
+      // end. If the cut-off point happens to fall in the address field, the
+      // conditions will be triggered.
+      if (address_column >= columns.size()) continue;
       uintptr_t address =
           strtoll(columns.at(address_column).c_str(), nullptr, 16);
-      CHECK_GT(address, 0);
+      if (address == 0) continue;
       result.insert(address);
-      ++start;  // Skip the found line.
     }
     return result;
   }