Migrate remaining tests on chromium.gpu.fyi to Swarming.

Migrate remaining tests on chromium.gpu.fyi to Swarming.

This means the testers do not need to be hardware based anymore.

R=kbr@chromium.org
BUG=98637

[Ken Russell (switch to Gerrit), 2016-08-05 01:11:06]

not lgtm

I'm not sure of the motivation for this CL, but all of the tests that can be
swarmed on the chromium.gpu.fyi waterfall already are. It looks like this CL
changes this flag for some of the remaining physical testers on this waterfall
which will never be converted to Swarming because we don't want to purchase
multiple machines of their kind.

If the intent here is to change the tests' specifications to all have
"can_use_on_swarming_builders" set to true, that should be done in
src/content/test/gpu/generate_buildbot_json.py even for the (one entry in)
NON_SWARMED_GTESTS, and presumably, the fact that Swarming is disabled for these
machines in
tools/build/scripts/slave/recipe_modules/chromium_tests/chromium_gpu_fyi.py will
take precedence.

[M-A Ruel, 2016-08-05 14:15:17]

On 2016/08/05 01:11:06, Ken Russell wrote:
> not lgtm
> 
> I'm not sure of the motivation for this CL

With the migration off buildbot, all builds will be driven by a recipe that
doesn't have access to the checkout, so all tests will have to be isolated one
day or another, or you'll be stuck in a one-off configuration.

Anyhow, there's no hurry a the moment, closing.

> , but all of the tests that can be
> swarmed on the chromium.gpu.fyi waterfall already are. It looks like this CL
> changes this flag for some of the remaining physical testers on this waterfall
> which will never be converted to Swarming because we don't want to purchase
> multiple machines of their kind.
> 
> If the intent here is to change the tests' specifications to all have
> "can_use_on_swarming_builders" set to true, that should be done in
> src/content/test/gpu/generate_buildbot_json.py even for the (one entry in)
> NON_SWARMED_GTESTS, and presumably, the fact that Swarming is disabled for
these
> machines in
> tools/build/scripts/slave/recipe_modules/chromium_tests/chromium_gpu_fyi.py
will
> take precedence.

[Ken Russell (switch to Gerrit), 2016-08-05 19:17:58]

On 2016/08/05 14:15:17, M-A Ruel wrote:
> On 2016/08/05 01:11:06, Ken Russell wrote:
> > not lgtm
> > 
> > I'm not sure of the motivation for this CL
> 
> With the migration off buildbot, all builds will be driven by a recipe that
> doesn't have access to the checkout, so all tests will have to be isolated one
> day or another, or you'll be stuck in a one-off configuration.
> 
> Anyhow, there's no hurry a the moment, closing.

This test target is already isolated. It wouldn't be a problem to invoke the
test locally via that isolate.



> 
> > , but all of the tests that can be
> > swarmed on the chromium.gpu.fyi waterfall already are. It looks like this CL
> > changes this flag for some of the remaining physical testers on this
waterfall
> > which will never be converted to Swarming because we don't want to purchase
> > multiple machines of their kind.
> > 
> > If the intent here is to change the tests' specifications to all have
> > "can_use_on_swarming_builders" set to true, that should be done in
> > src/content/test/gpu/generate_buildbot_json.py even for the (one entry in)
> > NON_SWARMED_GTESTS, and presumably, the fact that Swarming is disabled for
> these
> > machines in
> > tools/build/scripts/slave/recipe_modules/chromium_tests/chromium_gpu_fyi.py
> will
> > take precedence.