Only require iOS ninja bots on the commit queue

testing/commit_queue/config.json

Index: testing/commit_queue/config.json
diff --git a/testing/commit_queue/config.json b/testing/commit_queue/config.json
index da48bda5df2d2a8c11dbb507bb2f643b23810c43..7f8221abf5ed92af3dbcd2fceb8cf5386d85419e 100644
--- a/testing/commit_queue/config.json
+++ b/testing/commit_queue/config.json
@@ -72,21 +72,8 @@
             "tryserver.chromium.mac": {
               "mac_chromium_compile_dbg_ng": ["defaulttests"],
               "mac_chromium_rel_ng": ["defaulttests"],
-              "ios_dbg_simulator": [
-                  "compile",
-                  "base_unittests",
-                  "components_unittests",
-                  "content_unittests",
-                  "crypto_unittests",
-                  "url_unittests",
-                  "net_unittests",
-                  "sql_unittests",
-                  "ui_unittests",
-                  "sync_unit_tests",
-                  "gfx_unittests"
-              ],
-              "ios_rel_device_ng": ["defaulttests"],
-              "ios_rel_device_ninja_ng": ["defaulttests"]
+              "ios_dbg_simulator_ninja": ["defaulttests"],
+              "ios_rel_device_ninja": ["defaulttests"]

[jam, 2015/02/21 00:14:12]

actually, what do we gain from switching to ios_rel_device_ninja from
ios_rel_device_ng?

ios_rel_device_ninja bot appears to use a recipe that doesn't support
analyze.py, from looking at https://codereview.chromium.org/942953002/. So this
would be a regression.

[jam, 2015/02/23 15:14:30]

argh, I meant "from ios_rel_device_ninja_ng"

[smut, 2015/02/23 18:33:28]

I'll add an analyze.py step to these bots.

             },
             "tryserver.chromium.win": {
               "win8_chromium_rel": ["defaulttests"],