Made ChromeSyncShellTest.apk run on the fyi-tests bot.

build/android/buildbot/bb_device_steps.py

Index: build/android/buildbot/bb_device_steps.py
diff --git a/build/android/buildbot/bb_device_steps.py b/build/android/buildbot/bb_device_steps.py
index 8ff5a20ad63ac52922295728e8baaff4d1c3e8d6..29a63f9d3304ca33eab0230b457b4ac53cbc8a80 100755
--- a/build/android/buildbot/bb_device_steps.py
+++ b/build/android/buildbot/bb_device_steps.py
@@ -67,6 +67,11 @@ INSTRUMENTATION_TESTS = dict((suite.name, suite) for suite in [
       'ChromeShellTest',
       'chrome:chrome/test/data/android/device_files',
       constants.CHROME_SHELL_HOST_DRIVEN_DIR),
+    I('ChromeSyncShell',

[jbudorick, 2014/08/26 17:59:53]

Mentioned offline, but for the record: This will run ChromeSyncShellTests
wherever we run the other instrumentation tests on bots still running the
buildbot scripts. While this is what we eventually want to do, it isn't how we
want to start.

Add a separate test step command that just runs these sync tests and have the
fyi bots run that step.

+      'ChromeSyncShell.apk',
+      'org.chromium.chrome.browser.sync',
+      'ChromeSyncShellTest.apk',
+      'chrome:chrome/test/data/android/device_files'),
     I('AndroidWebView',
       'AndroidWebView.apk',
       'org.chromium.android_webview.shell',