Add sandbox_mac_unittests to the chromium.mac and chromium_trybot recipes.

testing/buildbot/chromium.mac.json

Index: testing/buildbot/chromium.mac.json
diff --git a/testing/buildbot/chromium.mac.json b/testing/buildbot/chromium.mac.json
index e095afe6e85d34814c5cce91e2eb7923fd7d1cf7..aa8e2854bd1c37bc234d8582796ecb4e4a235d8e 100644
--- a/testing/buildbot/chromium.mac.json
+++ b/testing/buildbot/chromium.mac.json
@@ -49,6 +49,7 @@
       "mojo_public_utility_unittests",
       "mojo_service_manager_unittests",
       "mojo_system_unittests",
+      {"test": "sandbox_mac_unittests", "args": ["--single-process-tests"]},

[Paweł Hajdan Jr., 2014/04/29 15:26:31]

Please *don't* use single-process-tests.

Why do you think it's needed? I'd be happy to help find a better solution.

[Robert Sesek, 2014/04/29 15:28:52]

If you use MultiprocessTest, it takes about twice as long and prints this every
time:

[43313:1287:0429/101233:2761157347505818:WARNING:test_suite.cc(171)] Test
launcher output path
/var/folders/93/t6gtn1pn4vx9j4wjnzvkzz8m003bw_/T/.org.chromium.Chromium.r22Lp0/test_results.xml
exists. Not adding test launcher result printer.

       {"test": "browser_tests", "shard_index": 2, "total_shards": 3}
     ]
   },
@@ -102,6 +103,7 @@
       "mojo_public_utility_unittests",
       "mojo_service_manager_unittests",
       "mojo_system_unittests",
+      {"test": "sandbox_mac_unittests", "args": ["--single-process-tests"]},
       {"test": "browser_tests", "shard_index": 2, "total_shards": 3}
     ]
   },
@@ -128,6 +130,7 @@
       "gfx_unittests",
       "media_unittests",
       "net_unittests",
+      {"test": "sandbox_mac_unittests", "args": ["--single-process-tests"]},
       {"test": "browser_tests", "shard_index": 1, "total_shards": 4}
     ]
   },
@@ -185,6 +188,7 @@
       "gfx_unittests",
       "media_unittests",
       "net_unittests",
+      {"test": "sandbox_mac_unittests", "args": ["--single-process-tests"]},
       {"test": "browser_tests", "shard_index": 1, "total_shards": 4}
     ]
   },