Flip remaining chromium_gn bots to the chromium recipe.

scripts/slave/recipe_modules/chromium_tests/trybots.py

Index: scripts/slave/recipe_modules/chromium_tests/trybots.py
diff --git a/scripts/slave/recipe_modules/chromium_tests/trybots.py b/scripts/slave/recipe_modules/chromium_tests/trybots.py
index 92046311044a36e0b8bae8a0ce63bc0a29d1abb8..41e4f4eb6b78008abbba01cbc9edaa95e33df0b0 100644
--- a/scripts/slave/recipe_modules/chromium_tests/trybots.py
+++ b/scripts/slave/recipe_modules/chromium_tests/trybots.py
@@ -643,6 +643,14 @@ TRYBOTS = freeze({
         'mastername': 'chromium.webkit',
         'buildername': 'WebKit Linux',
       }),
+      'v8_linux_chromium_gn_rel': simple_bot({
+        'mastername': 'client.v8.fyi',
+        'buildername': 'V8 Linux GN',

[Michael Achenbach, 2016/03/21 09:44:38]

Won't this need analyze_mode='compile'? It should be a compile-only bot, or is
that already given by having only a builder associated with it?

[Dirk Pranke, 2016/03/21 19:21:07]

You don't have to specify a 'tester' in order to run tests; if the 'buildername'
builder
is going to run tests, then the tryserver will also run the tests.

We could specify analyze_mode='compile' to be ultra-paranoid here, but since
'V8 Linux GN' doesn't run any tests anyway, you don't have to worry about it.

+      }),
+      'v8_android_chromium_gn_dbg': simple_bot({
+        'mastername': 'client.v8.fyi',
+        'buildername': 'V8 Android GN (dbg)',
+      }),
     },
   },
 })