Made ChromeShellSyncTests run alongside the other instrumentation tests.

Made ChromeShellSyncTests run alongside the other instrumentation tests.

The ChromeShellSyncTest tests have been running on some of the
chromium-fyi android bots. The tests have passed consistently for
several days and I am now moving them to run with the rest of the
instrumentation tests.

BUG=406538
Committed: https://crrev.com/94c8f1ad3b06bfa488fa263b88b65422c6fceb37
Cr-Commit-Position: refs/heads/master@{#301471}

[mikecase (-- gone --), 2014-10-25 00:49:34]

mikecase@chromium.org changed reviewers:
+ jbudorick@chromium.org

[mikecase (-- gone --), 2014-10-25 00:49:34]

Want to get this in on Monday. I'm guessing I'll have to make a recipe change as
well to get the bots on recipes to run these tests.

Also fyi, I fixed a minor issue. These tests do not need any test data but I was
previously using the ChromeShell test data. 


https://code.google.com/p/chromium/issues/detail?id=406538

[jbudorick, 2014-10-27 18:14:09]

https://codereview.chromium.org/680573004/diff/1/build/android/buildbot/bb_de...
File build/android/buildbot/bb_device_steps.py (right):

https://codereview.chromium.org/680573004/diff/1/build/android/buildbot/bb_de...
build/android/buildbot/bb_device_steps.py:80: None),
Why didn't the device_files folder make the jump?

[mikecase (-- gone --), 2014-10-27 18:21:39]

https://codereview.chromium.org/680573004/diff/1/build/android/buildbot/bb_de...
File build/android/buildbot/bb_device_steps.py (right):

https://codereview.chromium.org/680573004/diff/1/build/android/buildbot/bb_de...
build/android/buildbot/bb_device_steps.py:80: None),
On 2014/10/27 18:14:09, jbudorick wrote:
> Why didn't the device_files folder make the jump?

I tested it locally and the ChromeSyncTest doesn't need any device files. It was
just a small mistake I made when I initially set up these tests.

[jbudorick, 2014-10-27 20:44:33]

lgtm

[mikecase (-- gone --), 2014-10-27 20:47:40]

The CQ bit was checked by mikecase@chromium.org

[commit-bot: I haz the power, 2014-10-27 20:48:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/680573004/1

[commit-bot: I haz the power, 2014-10-27 21:21:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-27 21:21:19]

Try jobs failed on following builders:
  linux_chromium_gn_dbg on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mikecase (-- gone --), 2014-10-27 21:35:27]

The CQ bit was checked by mikecase@chromium.org

[commit-bot: I haz the power, 2014-10-27 21:37:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/680573004/1

[commit-bot: I haz the power, 2014-10-27 23:09:45]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-27 23:10:24]

Patchset 1 (id:??) landed as
https://crrev.com/94c8f1ad3b06bfa488fa263b88b65422c6fceb37
Cr-Commit-Position: refs/heads/master@{#301471}