Infra setup for Hoverboard test slave

scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py

Index: scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py
diff --git a/scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py b/scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py
index a9ccfa2722e4374c235d9a0294d10e6a3f6a0995..e8f75577fc9de7c5c8fc02a54e4c768f225c960e 100644
--- a/scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py
+++ b/scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py
@@ -2187,6 +2187,29 @@ SPEC = {
         'platform': 'win',
       },
     },
+    'Android VR Tests': {
+      'chromium_config': 'android',
+      'gclient_config': 'chromium',
+      'gclient_apply_config': ['android'],
+      'chromium_config_kwargs': {
+        'BUILD_CONFIG': 'Debug',
+        'TARGET_BITS': 32,

[jbudorick, 2016/09/01 18:48:01]

You shouldn't need to set TARGET_BITS.

[bsheedy, 2016/09/01 21:24:26]

Done.

+        'TARGET_PLATFORM': 'android',
+      },
+      'bot_type': 'tester',
+      'parent_buildername': 'Android Builder (dbg)',
+      'android_config': 'arm64_builder_mb'

[jbudorick, 2016/09/01 18:48:01]

I know I said to switch this from main_builder_mb, but with this triggering off
of an arm builder rather than an arm64 builder, I might have been wrong. (I
don't think we have any bots that do this at the moment.)

[bsheedy, 2016/09/01 21:24:26]

Done.

+      'root_devices': True,
+      'test_generators': [
+        steps.generate_gtest,
+        steps.generate_script,
+        steps.generate_isolated_script,
+        steps.generate_instrumentation_test,
+      ],
+      'testing': {
+        'platform': 'linux',
+      },
+    },
 
     'Linux remote_run Builder': {
       'chromium_config': 'chromium',