[mojo-edk] Fix test expectations for official builds

mojo/edk/system/options_validation_unittest.cc

 // Copyright 2014 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/options_validation.h"
 
 #include <stddef.h>
 #include <stdint.h>
 
 #include "mojo/public/c/system/macros.h"
@@ skipping 77 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(OptionsValidationTest, InvalidDeath) {
+#if defined(OFFICIAL_BUILD)
+  const char kMemoryCheckFailedRegex[] = "";
+#else
   const char kMemoryCheckFailedRegex[] = "Check failed";
+#endif
 
   // Null:
   EXPECT_DEATH_IF_SUPPORTED(
       { UserOptionsReader<TestOptions> reader((nullptr)); },
       kMemoryCheckFailedRegex);
 
   // Unaligned:
   EXPECT_DEATH_IF_SUPPORTED(
       {
         UserOptionsReader<TestOptions> reader(
@@ skipping 12 matching lines @@
                                    : reinterpret_cast<TestOptions*>(&buffer[0]);
         options->struct_size = static_cast<uint32_t>(sizeof(TestOptions));
         UserOptionsReader<TestOptions> reader(options);
       },
       kMemoryCheckFailedRegex);
 }
 
 }  // namespace
 }  // namespace edk
 }  // namespace mojo