[mojo-edk] Fix test expectations for official builds

mojo/edk/system/core_unittest.cc

 // Copyright 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "mojo/edk/system/core.h"
 
 #include <stdint.h>
 
 #include <limits>
 
@@ skipping 427 matching lines @@
   }
 }
 
 // These test invalid arguments that should cause death if we're being paranoid
 // about checking arguments (which we would want to do if, e.g., we were in a
 // true "kernel" situation, but we might not want to do otherwise for
 // performance reasons). Probably blatant errors like passing in null pointers
 // (for required pointer arguments) will still cause death, but perhaps not
 // predictably.
 TEST_F(CoreTest, InvalidArgumentsDeath) {
+#if defined(OFFICIAL_BUILD)
+  const char kMemoryCheckFailedRegex[] = "";
+#else
   const char kMemoryCheckFailedRegex[] = "Check failed";
+#endif
 
   // |WaitMany()|:
   {
     MojoHandle handle = MOJO_HANDLE_INVALID;
     MojoHandleSignals signals = ~MOJO_HANDLE_SIGNAL_NONE;
     ASSERT_DEATH_IF_SUPPORTED(
         core()->WaitMany(nullptr, &signals, 1, MOJO_DEADLINE_INDEFINITE,
                          nullptr, nullptr),
         kMemoryCheckFailedRegex);
     ASSERT_DEATH_IF_SUPPORTED(
@@ skipping 802 matching lines @@
   ASSERT_EQ(MOJO_RESULT_BUSY, waiter.result);
 
   ASSERT_EQ(MOJO_RESULT_OK, core()->Close(h));
 }
 
 // TODO(vtl): Test |DuplicateBufferHandle()| and |MapBuffer()|.
 
 }  // namespace
 }  // namespace edk
 }  // namespace mojo