Android: Integrates native and java SystemMonitor.

testing/android/java/src/org/chromium/native_test/ChromeNativeTestActivity.java

Index: testing/android/java/src/org/chromium/native_test/ChromeNativeTestActivity.java
diff --git a/testing/android/java/src/org/chromium/native_test/ChromeNativeTestActivity.java b/testing/android/java/src/org/chromium/native_test/ChromeNativeTestActivity.java
index b984c4868a79155bb9f18ac0f21396033ac8da6b..77022506daa6b5ea930f6d9a5741840bcfadeb68 100644
--- a/testing/android/java/src/org/chromium/native_test/ChromeNativeTestActivity.java
+++ b/testing/android/java/src/org/chromium/native_test/ChromeNativeTestActivity.java
@@ -12,6 +12,7 @@ import android.os.Handler;
 import android.util.Log;
 
 import org.chromium.base.PathUtils;
+import org.chromium.base.SystemMonitor;
 
 import java.io.File;
 
@@ -40,6 +41,9 @@ public class ChromeNativeTestActivity extends Activity {
         // Needed by path_utils_unittest.cc
         PathUtils.setPrivateDataDirectorySuffix("chrome");
 
+        // Needed by system_monitor_unittest.cc

[Satish, 2012/10/08 13:58:10]

Since this is required only by 1 test, it is overhead for all the other tests..
but because it is a c++ test I guess there is no alternative other than putting
it in common code here.

[bulach, 2012/10/08 14:01:04]

thanks! that's correct, there are no alternatives, as the c++ test requires this
to be set up by the application / harness... note though that the overhead is
insignificant, as this is run per test suite, not per test..

+        SystemMonitor.createForTests(this);
+
         try {
             loadLibrary();
             Bundle extras = this.getIntent().getExtras();