Add step to process Render Test results.

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 1808 matching lines @@
         'BUILD_CONFIG': 'Debug',
         'TARGET_BITS': 32,
         'TARGET_PLATFORM': 'android',
       },
       'bot_type': 'tester',
       'parent_buildername': 'Android Builder (dbg)',
       'android_config': 'non_device_wipe_provisioning',
       'root_devices': True,
       'tests': [
         steps.GTestTest('gfx_unittests'),
+        steps.AndroidInstrumentationTest('ChromePublicTest'),
+        steps.UploadRenderTestFailures(render_results_dir='chrome/test/data/android/render_tests'),

[jbudorick, 2016/10/25 17:03:40]

:O

Does this need to be a separately configured test? Can we do it some other way?

[mikecase (-- gone --), 2016/10/25 20:53:33]

hmmmm, well, I could add an argument to run_instrumentation_test() function in
chromium_android/api.py. Done. This seems a bit better.

       ],
       'testing': {
         'platform': 'linux',
       },
     },
 
     'Android Remoting Tests': {
       'chromium_config': 'android',
       'gclient_config': 'chromium',
       'gclient_apply_config': ['android'],
@@ skipping 258 matching lines @@
         'TARGET_PLATFORM': 'win',
         'TARGET_BITS': 32,
       },
       'bot_type': 'builder_tester',
       'testing': { 'platform': 'win', },
       'use_isolate': True,
       'enable_swarming': True,
     },
   },
 }