Added new slaves and spec files for GPU FYI bots running Chromium recipe.

masters/master.chromium.gpu.fyi/slaves.cfg

Index: masters/master.chromium.gpu.fyi/slaves.cfg
diff --git a/masters/master.chromium.gpu.fyi/slaves.cfg b/masters/master.chromium.gpu.fyi/slaves.cfg
index a7a9228ca6e9ac322e0057c496369b983dae61b2..e4115919dfb8286470ca99d8722cce4540699d67 100644
--- a/masters/master.chromium.gpu.fyi/slaves.cfg
+++ b/masters/master.chromium.gpu.fyi/slaves.cfg
@@ -286,4 +286,96 @@ slaves = [
     'version': 'precise',
     'bits': '64',
   },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'slave60-c1',
+    'builder': 'GPU NextGen Linux Builder',
+    'os': 'linux',
+    'version': 'precise',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Release',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'slave61-c1',
+    'builder': 'GPU NextGen Linux Builder (dbg)',
+    'os': 'linux',
+    'version': 'precise',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Debug',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'slave62-c1',
+    'builder': 'Linux NextGen Release (NVIDIA)',
+    'os': 'linux',
+    'version': 'precise',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Release',
+    # TODO(kbr): is this needed or will it conflict with the Chromium

[Ken Russell (switch to Gerrit), 2015/12/29 03:35:52]

I'm 99% sure that in order for these new testers to work correctly, I need to
remove the "triggered_by" property. I added it specially for the
recipe_master_helper to be able to trigger the GPU testers from the builders.
However, it looks like the Chromium recipe uses recipe-based triggers, so the
testers should be added only to the buildbot "builders", and not the
"schedulers". Can anyone confirm whether that's correct?

(The chromium.gpu and chromium.gpu.fyi waterfalls are the only ones using the
recipe_master_helper -- it's very useful, and eliminates a lot of boilerplate
for the waterfalls. I studied the differences between master.chromium.gpu.fyi
and master.chromium.linux.)

[tandrii(chromium), 2015/12/29 11:19:30]

i'm with you here, but also for 99% - don't know for sure. Sergey - can you
verify this claim?

[Sergey Berezin, 2015/12/29 18:25:36]

I looked at it together with dnj@, and apparently 'triggered_by' will not be
used at all. Instead, what you did with in the config specifying the parent
builder is apparently enough to set up all the triggers. Disclaimer - I didn't
actually use it myself, so the same 99% :-)

[Ken Russell (switch to Gerrit), 2015/12/30 02:05:22]

recipe_master_helper.py, which is used to set up this waterfall, pays attention
to the "triggered_by" property. I'm pretty sure I need to modify it to avoid
setting up a scheduler and Triggerable for these testers.

+    # recipe's triggering mechanism?
+    'triggered_by': 'GPU NextGen Linux Builder',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'slave63-c1',
+    'builder': 'Linux NextGen Debug (NVIDIA)',
+    'os': 'linux',
+    'version': 'precise',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Debug',
+    # TODO(kbr): is this needed or will it conflict with the Chromium
+    # recipe's triggering mechanism?
+    'triggered_by': 'GPU NextGen Linux Builder (dbg)',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'vm71-m1',
+    'builder': 'GPU NextGen Mac Builder',
+    'os': 'mac',
+    'version': '10.10',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Release',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'vm72-m1',
+    'builder': 'GPU NextGen Mac Builder (dbg)',
+    'os': 'mac',
+    'version': '10.10',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Debug',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'vm73-m1',
+    'builder': 'Mac NextGen 10.10 Retina Release (AMD)',
+    'os': 'mac',
+    'version': '10.10',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Release',
+    # TODO(kbr): is this needed or will it conflict with the Chromium
+    # recipe's triggering mechanism?
+    'triggered_by': 'GPU NextGen Mac Builder',
+  },
+  {
+    'master': 'ChromiumGPUFYI',
+    'hostname': 'vm74-m1',
+    'builder': 'Mac NextGen 10.10 Retina Debug (AMD)',
+    'os': 'mac',
+    'version': '10.10',
+    'bits': '64',
+    'recipe': 'chromium',
+    'build_config': 'Debug',
+    # TODO(kbr): is this needed or will it conflict with the Chromium
+    # recipe's triggering mechanism?
+    'triggered_by': 'GPU NextGen Mac Builder (dbg)',
+  },
 ]