Linux sandbox: add basic Yama support

sandbox/linux/tests/unit_tests.h

 // Copyright (c) 2012 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.
 
 #ifndef SANDBOX_LINUX_TESTS_UNIT_TESTS_H__
 #define SANDBOX_LINUX_TESTS_UNIT_TESTS_H__
 
 #include "base/basictypes.h"
 #include "build/build_config.h"
 #include "testing/gtest/include/gtest/gtest.h"
 
 namespace sandbox {
 
 // Has this been compiled to run on Android?
 bool IsAndroid();
 
 bool IsArchitectureArm();
 
 // Is Valgrind currently being used?
 bool IsRunningOnValgrind();
 
 #if defined(THREAD_SANITIZER)
 #define DISABLE_ON_TSAN(test_name) DISABLED_##test_name
 #else
 #define DISABLE_ON_TSAN(test_name) test_name
 #endif  // defined(THREAD_SANITIZER)
 
+#if defined(OS_ANDROID)
+#define DISABLE_ON_ANDROID(test_name) DISABLED_##test_name
+#else
+#define DISABLE_ON_ANDROID(test_name) test_name
+#endif
+
 // While it is perfectly OK for a complex test to provide its own DeathCheck
 // function. Most death tests have very simple requirements. These tests should
 // use one of the predefined DEATH_XXX macros as an argument to
 // SANDBOX_DEATH_TEST(). You can check for a (sub-)string in the output of the
 // test, for a particular exit code, or for a particular death signal.
 // NOTE: If you do decide to write your own DeathCheck, make sure to use
 //       gtests's ASSERT_XXX() macros instead of SANDBOX_ASSERT(). See
 //       unit_tests.cc for examples.
 #define DEATH_SUCCESS() sandbox::UnitTests::DeathSuccess, NULL
 #define DEATH_MESSAGE(msg)          \
@@ skipping 88 matching lines @@
                             const std::string& msg,
                             const void* aux);
 
  private:
   DISALLOW_IMPLICIT_CONSTRUCTORS(UnitTests);
 };
 
 }  // namespace
 
 #endif  // SANDBOX_LINUX_TESTS_UNIT_TESTS_H__