Remove the android_isolate_path option from LocalGTestTest.

scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 from . import steps
 
 RESULTS_URL = 'https://chromeperf.appspot.com'
 
 
 KITCHEN_TEST_SPEC = {
@@ skipping 1585 matching lines @@
       'testing': { 'platform': 'linux', },
       # Workaround so that recipes doesn't add random build targets to our
       # compile line. We want to build everything.
       'add_tests_as_compile_targets': False,
       'root_devices': True,
       'test_generators': [
         steps.generate_gtest,
         steps.generate_junit_test,
       ],
       'tests': [
-        steps.GTestTest(
-            'components_browsertests',
-            android_isolate_path='components/components_browsertests.isolate',
-            android_tool='asan'),
+        steps.GTestTest('components_browsertests', android_tool='asan'),
         steps.GTestTest('gfx_unittests', android_tool='asan'),

[Dirk Pranke, 2016/08/09 23:52:16]

why are these even still listed here, rather than in the source-side files?
because of the android_tool arg?

[jbudorick, 2016/08/09 23:55:28]

AFAICT yes, because the gtest generator doesn't take android_tool at the moment.
I could change that and move these src/-side in a subsequent CL if you'd like.

       ],
     },
     'ClangToTMac': {
       'chromium_config': 'clang_tot_mac',
       'gclient_config': 'chromium',
       'chromium_apply_config': ['mb'],
       'chromium_config_kwargs': {
         'BUILD_CONFIG': 'Release',
         'TARGET_BITS': 64,
       },
@@ skipping 657 matching lines @@
         steps.generate_gtest,
         steps.generate_script,
         steps.generate_isolated_script,
       ],
       'testing': { 'platform': 'win', },
       'use_isolate': True,
       'enable_swarming': True,
     },
   },
 }