Add a run_eslint wrapper script

catapult_build/build_steps.py

 # Copyright 2016 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.
 
 import argparse
 import json
 import os
 import sys
 
 # This is the list of tests to run. It is a dictionary with the following
@@ skipping 69 matching lines @@
         'path': 'devil/bin/run_py_devicetests',
         'disabled': ['win', 'mac', 'linux']
     },
     {
         'name': 'Devil Python Tests',
         'path': 'devil/bin/run_py_tests',
         'disabled': ['mac', 'win'],
     },
     {
         'name': 'Node Smoke Test',
-        'path': 'common/node_runner/bin/test_node_for_smoke',
+        'path': 'common/eslint/bin/run_eslint',
+        'additional_args': ['--help'],

[nednguyen, 2016/09/23 13:22:13]

Hmhh, the point of running this is we can make sure that we are able to execute
node_js across platforms hence once people update the node_js ref, we have more
guarantee that things won't break. Running --help seems to defeat that purpose.

[nednguyen, 2016/09/23 13:24:26]

I think it's best to create a smoke unittest for eslint, s.t like
eslint_unittest that run lint on a test html file.

Then here, we run: common/eslint/bin/run_tests

         'disabled': ['android'],
     },
     {
         'name': 'Py-vulcanize Tests',
         'path': 'third_party/py_vulcanize/bin/run_py_tests',
         'additional_args': ['--no-install-hooks'],
         'disabled': ['android'],
     },
     {
         'name': 'Systrace Tests',
@@ skipping 136 matching lines @@
       step['env']['CHROME_DEVEL_SANDBOX'] = '/opt/chromium/chrome_sandbox'
     if test.get('outputs_presentation_json'):
       step['outputs_presentation_json'] = True
     steps.append(step)
   with open(args.output_json, 'w') as outfile:
     json.dump(steps, outfile)
 
 
 if __name__ == '__main__':
   main(sys.argv[1:])