Run google_apis_unittests on chromeos bots.

masters/master.chromium.chromiumos/master_chromiumos_cfg.py

Index: masters/master.chromium.chromiumos/master_chromiumos_cfg.py
diff --git a/masters/master.chromium.chromiumos/master_chromiumos_cfg.py b/masters/master.chromium.chromiumos/master_chromiumos_cfg.py
index 64a1f7bf1e8e1e1bd0538db9836de85d46b1f241..9e14c3b7936296c8d361c6ec3a256cbd38e2eb03 100644
--- a/masters/master.chromium.chromiumos/master_chromiumos_cfg.py
+++ b/masters/master.chromium.chromiumos/master_chromiumos_cfg.py
@@ -40,6 +40,7 @@ sharded_tests = [
   'content_unittests',
   'crypto_unittests',
   'device_unittests',
+  'google_apis_unittests',

[ghost stip (do not use), 2013/11/12 19:16:28]

if it's on gatekeeper, then it needs to be in commit-queue's projects.py.

[tfarina, 2013/11/12 19:32:14]

of course I didn't know I was putting it on a gatekeeper.

Is gatekeeper a tree closer? Is that what it means?

I'll checkout commit-queue code and add the entries for google_apis_unittests
here:

https://chromium.googlesource.com/chromium/tools/commit-queue/+/master/projec...

   'gpu_unittests',
   'jingle_unittests',
   'media_unittests',
@@ -70,6 +71,7 @@ linux_chromeos_tests = [
   ('crypto_unittests', 'crypto_unittests', 1),
   ('dbus', 'dbus_unittests', 1),
   ('device_unittests', 'device_unittests', 1),
+  ('google_apis_unittests', 'google_apis_unittests', 1),
   ('gpu', 'gpu_unittests', 1),
   ('googleurl', 'url_unittests', 1),
   (None, 'url_unittests', 1),