Added sandbox_linux_unittests to ARM trybot

testing/buildbot/chromium_arm.json

Index: testing/buildbot/chromium_arm.json
diff --git a/testing/buildbot/chromium_arm.json b/testing/buildbot/chromium_arm.json
index 5eda562fd6d000cf8138ec1a62d71e690557ad1d..19c3719c5c772795411e4bbca5b9419820b6c12e 100644
--- a/testing/buildbot/chromium_arm.json
+++ b/testing/buildbot/chromium_arm.json
@@ -1,8 +1,10 @@
 {
   "compile_targets": [
-    "browser_tests_run"
+    "browser_tests_run",
+    "sandbox_linux_unittests_run"
   ],
   "gtest_tests": [
-    "browser_tests"
+    "browser_tests",
+    "sandbox_linux_unittests"

[jln (very slow on Chromium), 2014/06/20 00:44:03]

Ohh, I forgot: is there a way here to add
--test-launcher-print-test-stdio=always ?

This is for instance what's in testing/buildbot/chromium_trybot.json and it's
really helpful to control what features the kernel supports.

[nodir, 2014/06/20 01:03:53]

Since currently there is no way to pass cmd line args from a builder to a tester
(only a test name), so we keep the cmd line args separately (terrible) the
chromium_isolate recipe. This will be fixed once http://crbug.com/361841 is
fixed

CL: https://codereview.chromium.org/344793011

I'll put the test filter there.

   ]
 }