Add a Mojo EDK for Chrome that uses one OS pipe per message pipe.

mojo/edk/system/test_utils.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 "third_party/mojo/src/mojo/edk/system/test_utils.h"
+#include "mojo/edk/system/test_utils.h"
 
 #include <limits>
 
 #include "base/logging.h"
 #include "base/test/test_timeouts.h"
 #include "base/threading/platform_thread.h"  // For |Sleep()|.
 #include "build/build_config.h"
 
 namespace mojo {
-namespace system {
+namespace edk {
 namespace test {
 
 MojoDeadline DeadlineFromMilliseconds(unsigned milliseconds) {
   return static_cast<MojoDeadline>(milliseconds) * 1000;
 }
 
 MojoDeadline EpsilonDeadline() {
 // Originally, our epsilon timeout was 10 ms, which was mostly fine but flaky on
 // some Windows bots. I don't recall ever seeing flakes on other bots. At 30 ms
 // tests seem reliable on Windows bots, but not at 25 ms. We'd like this timeout
@@ skipping 36 matching lines @@
   start_time_ = base::TimeTicks::Now();
 }
 
 MojoDeadline Stopwatch::Elapsed() {
   int64_t result = (base::TimeTicks::Now() - start_time_).InMicroseconds();
   // |DCHECK_GE|, not |CHECK_GE|, since this may be performance-important.
   DCHECK_GE(result, 0);
   return static_cast<MojoDeadline>(result);
 }
 
+
+MojoSystemTest::MojoSystemTest()
+    : test_io_thread_(base::TestIOThread::kAutoStart),
+      ipc_support_(test_io_thread_.task_runner()) {
+}
+
+MojoSystemTest::~MojoSystemTest() {
+}
+
 }  // namespace test
-}  // namespace system
+}  // namespace edk
 }  // namespace mojo