7e10708628c1bd21d6a08adab3913c2275204df9 |
|
12-Jan-2017 |
Prathmesh Prabhu <pprabhu@chromium.org> |
run_pylint: Tighten exception capture in main. We want to avoid printing a stack trace when a lint check fails. But if pytlint chokes on a file for some other reason, we want that trace. BUG=None. TEST=./utils/run_pylint throws an exception trace (that's a separate bug) Change-Id: Ib002d99707a8707cb5f3ce2de3079a8f37f32b08 Reviewed-on: https://chromium-review.googlesource.com/427409 Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>
/external/autotest/utils/run_pylint.py
|
5dab08c529d9a914665cea9c542b51765e264bf5 |
|
12-Jan-2017 |
Prathmesh Prabhu <pprabhu@chromium.org> |
run_pylint: Add site-packages/ to blacklist. Stuff in site-packages does not conform to autotest coding style and should be ignored. BUG=None. TEST=None. Change-Id: I8d24691d2ce606ea89e3f99c6e5b16e39a59a2dd Reviewed-on: https://chromium-review.googlesource.com/427410 Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>
/external/autotest/utils/run_pylint.py
|
baabef2eae533784f861b33ab41711616d399f04 |
|
04-Nov-2014 |
Prashanth Balasubramanian <beeps@google.com> |
[autotest] Puppy lab testing environment. This is the first commit for a more reliable testing environment for ChromeOS lab infrastructure. It creates a class capable of mocking out job results without turning the parsing operation into a no-op. This allows us to schedule tests against fake DUTs without actually needing to ssh-into them, which is pretty much all that dummy_Pass actually does. The cl also sneaks in a fix to hide the exception stack trace from run_pylint. TEST=Ran bvt. BUG=chromium:423225,chromium:425347 Change-Id: I5ecbcf1ff08bf9f45af26333c2ccb4c4022a97d6 Reviewed-on: https://chromium-review.googlesource.com/227783 Reviewed-by: Prashanth B <beeps@chromium.org> Commit-Queue: Prashanth B <beeps@chromium.org> Tested-by: Prashanth B <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
a528758835ee15acbdc06b4d7c56cb3f52d21b41 |
|
15-Aug-2014 |
Dan Shi <dshi@chromium.org> |
Handle pylint change in newer version when handling docstring check. After pylint is upgraded to 1.1.0, the internal dict _messages is no longer indexed by id, e.g., 'C0111', instead, it's indexed by a 'descriptor' like messing-docstring. This CL handles such change for pylint after 1.1.0. BUG=None TEST=utils/run_pylint and see missing docstrings are checked properly. Change-Id: Ib8f4af88767313c05c590040ae2169f786930170 Reviewed-on: https://chromium-review.googlesource.com/212522 Tested-by: Dan Shi <dshi@chromium.org> Reviewed-by: Prashanth B <beeps@chromium.org> Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/utils/run_pylint.py
|
2d8047e8b2d901bec66d483664d8b6322501d245 |
|
28-Apr-2014 |
Prashanth B <beeps@google.com> |
[autotest] In process request/host caching for the rdb. This cl implements an in process host cache manager for the rdb. The following considerations were taken into account while designing it: 1. The number of requests outweigh the number of leased hosts 2. The number of net hosts outweighs the number of leased hosts 3. The 'same' request can consult the cache within the span of a single batched request. These will only be same in terms of host labels/acls required, not in terms of priority or parent_job_id. Resulting ramifications: 1. We can't afford to consult the database for each request. 2. We can afford to refresh our in memory representation of a host just before leasing it. 3. Leasing a host can fail, as we might be using a stale cached host. 4. We can't load a map of all hosts <-> labels each request. 5. Invalidation is hard for most sane, straight-forward choices of keying hosts against requests. 6. Lower priority requests will starve if they try to lease the same hosts taken by higher priority requests. Main design tenets: 1. We can tolerate some staleness in the cache, since we're going to make sure the host is unleased just before using it. 2. If a job hits a stale cache line it tries again next tick. 3. Trying to invalidate the cache within a single batched request will be unnecessarily complicated and error prone. Instead, to prevent starvation, each request only invalidates its cache line, by removing the hosts it has just leased. 4. The same host may be preset in 2 different cache lines but this won't matter because each request will check the leased bit in real time before acquiring it. 5. The entire cache is invalidated at the end of a batched request. TEST=Ran suites, unittests. BUG=chromium:366141 DEPLOY=Scheduler Change-Id: Iafc3ffa876537da628c52260ae692bc2d5d3d063 Reviewed-on: https://chromium-review.googlesource.com/197788 Reviewed-by: Dan Shi <dshi@chromium.org> Tested-by: Prashanth B <beeps@chromium.org> Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
5e2bb4aa28611aaacaa8798fd07943ede1df46c6 |
|
28-Oct-2013 |
beeps <beeps@chromium.org> |
[autotest] Scheduler refactor. Break scheduler into simpler modules. This change also modifies run_pylint to check for undefined variables. BUG=chromium:312338 TEST=Ran smoke suite against multiple duts. Triggered agents like repair, verify etc. Pylint, Unittests. DEPLOY=scheduler Change-Id: Ibd685a27b5b50abd26cdf2976ac4189c3e9acc0a Reviewed-on: https://chromium-review.googlesource.com/174080 Commit-Queue: Prashanth B <beeps@chromium.org> Tested-by: Prashanth B <beeps@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org>
/external/autotest/utils/run_pylint.py
|
f9a36511e83c4ebeaa6192ca7219895597284681 |
|
14-Jun-2013 |
Keyar Hood <keyar@chromium.org> |
Autotest: Test health script uses Django models. Instead of doing raw SQL queries, the complete_failures.py script will use Django models to check the database. BUG=chromium:249571 DEPLY=none TEST=Manually ran script. Change-Id: I89b02bf4ad0c0951ae0e74b91bebdeff99ca0de4 Reviewed-on: https://gerrit.chromium.org/gerrit/58618 Reviewed-by: Dennis Jeffrey <dennisjeffrey@chromium.org> Commit-Queue: Keyar Hood <keyar@chromium.org> Tested-by: Keyar Hood <keyar@chromium.org>
/external/autotest/utils/run_pylint.py
|
e19d303a6718cbd9995e27485554212b63a0a701 |
|
30-May-2013 |
beeps <beeps@chromium.org> |
[autotest] pylint ignores setters, getters and special modules. Prior to this change pylint only ignored one special module, common. This change makes it so we can specify a list of modules to ignore. BUG=chromium:239949 TEST=Successfully uploaded this cl run_pylint on: 1. modules with getters and setters. 2. a change which uses setup_django_lite. 3. module with actual unused modules. 4. repeat within the chroot. Change-Id: I2cbd2b654cfc78323b9dd840c1822b2a60b02e83 Reviewed-on: https://gerrit.chromium.org/gerrit/51002 Tested-by: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
c38decc40a5ed6e3ee0462388074f3dd80c250cb |
|
30-Apr-2013 |
beeps <beeps@chromium.org> |
[autotest] Pylint shouldn't check ancestors if none exist. TEST=Ran pylint on a function called run_once without ancestors. Also ran it on some offending cls. BUG=chromium:235685 Change-Id: Icfd2a389bc955ed22c533c1fab684d15c415268b Reviewed-on: https://gerrit.chromium.org/gerrit/49577 Tested-by: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
12a3c882b514db90fcadfd1e11d1af214d1e664a |
|
22-Apr-2013 |
beeps <beeps@chromium.org> |
[autotest] Pylint shouldn't fail with empty file paths. In order to control exceptions, messages and pylint exiting, we invoke the Run method on pylint directly instead of shelling out and calling the module itself. This Run method takes the command line arguments and a list of files to parse. Many of these command line arguments trigger the execution of a callback function that will simply exit when the list of files to check is empty. Normal invocations of pylint are not expected to reach this stage, but we do because of the direct invocation mentioned. TEST=Ran repo upload . with the offending commit which contains a list of non-py files and made sure we don't exit. BUG=None Change-Id: Id2ea1ac8e025e235c35d1ccf08859ead1d6d7cfb Reviewed-on: https://gerrit.chromium.org/gerrit/48810 Reviewed-by: Alex Miller <milleral@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
98365d89774921bd065fe4bf2d273be7e100af43 |
|
21-Feb-2013 |
beeps <beeps@chromium.org> |
[autotest] Pylint checks committed versions of a file. The contents of a file in the git work tree can differ from the contents of a file in the HEAD commit. This is problematic for the following reasons: 1. The uploader may not have committed their changes. 2. The uploader might repo upload a stack of commits each of which builds upon the other. In this case run_hooks is invoked on each commit and running pylint on the work tree version of the file doesn't make sense. To work around this we invoke run pylint on a temp file, into which we've 'git show'n the committed version of each file, so we're only checking that specific commit. The change also batch processes files so we get consolidated error reports and excuses run_once, initialize and cleanup from needing a docstring. The 'git show' mentioned above is achieved through a GitRepo object. This commit also allows revision_control to run git commands without requiring a giturl, and adds unittests to check that commands that do need a giturl raise an exception if called without one. TEST=Ran pylint with malformed non committed/committed files. Made sure pylint displays multiple errors of the same type in one report. BUG=None Change-Id: I82329d14c0334752941150c61d91e2e723b0c4d2 Reviewed-on: https://gerrit.chromium.org/gerrit/43697 Commit-Queue: Scott Zawalski <scottz@chromium.org> Reviewed-by: Scott Zawalski <scottz@chromium.org> Tested-by: Scott Zawalski <scottz@chromium.org>
/external/autotest/utils/run_pylint.py
|
d5fb41b2f7349b9d10d984856e85581092148a8d |
|
11-Apr-2013 |
beeps <beeps@chromium.org> |
[Autotest] Pylint checks all files if the only change is to remove a file. As an artifact of the old run_pylint we maintained the option of checking all files in a directory if the list of presubmit files is empty. This allows one to check all of autotest by invoking ./utils/run_pylint.py. We should instead only do this if the PRESUBMIT_FILES environment variable is not set. If the list is empty we could still be removing files, and we don't need to check them. TEST=Ran repo upload . with the offending cl and made sure pylint didn't complain. BUG=None Change-Id: Ie38b7a2a28b89677a56b0f36f06981aaedf7be3d Reviewed-on: https://gerrit.chromium.org/gerrit/47912 Reviewed-by: Tan Gao <tgao@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
ae6acd9b3e1c6f56310cdb4e05737122b7b2818c |
|
07-Feb-2013 |
Chris Sosa <sosa@chromium.org> |
Override devserver_up's default timeout to return immediately in au test. Since we control this devserver, we want to control how long to wait for the devserver to be up. This CL slightly refactors the devserver api to allow callers to override the retry.retry timeout in some rpc's. Also fixed the pylintrc to skip **kwargs, *args, and cls. BUG=None TEST=Pylint so far + unittests Change-Id: Ie454e81be8940bdc7b8530bd682dab80910b8b83 Reviewed-on: https://gerrit.chromium.org/gerrit/43480 Tested-by: Chris Sosa <sosa@chromium.org> Reviewed-by: Brian Harring <ferringb@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/utils/run_pylint.py
|
c9224b4d7bb1df2b7ecbd8e31d929ca586c76d7a |
|
20-Feb-2013 |
Prashanth Balasubramanian <beeps@chromium.org> |
Revert "[autotest] run_pylint now notices uncommitted files." This reverts commit 723877f4eddc8409e822bdf7ebea536209ebbb5a Change-Id: Ia2e1381da2a9a8b2defd2bbeec24291a235d3edd Reviewed-on: https://gerrit.chromium.org/gerrit/43615 Reviewed-by: Alex Miller <milleral@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
723877f4eddc8409e822bdf7ebea536209ebbb5a |
|
15-Feb-2013 |
beeps <beeps@chromium.org> |
[autotest] run_pylint now notices uncommitted files. Pylint will now reject any file that's part of the list of files to commit but differs from the version in the working tree, since it only checks the file in the working tree. TEST=None BUG=chromium-os:38896 Change-Id: I799cdff0836f82e4662682e4d697d9ad1129e20f Reviewed-on: https://gerrit.chromium.org/gerrit/43417 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
1b6433bdf3ea1f1fffaa523c6aa0411e3d8f4ece |
|
01-Feb-2013 |
beeps <beeps@chromium.org> |
[autotest] Disables docstring checking for private methods and imports. Also enables pylint checking for string interpolation in logging statements. Affected pylint error codes: W1201, C0111. TEST=Creates files with private methods that lack a docstring. Forced string interpolation in logging statementes. BUG=None Change-Id: I9ed5aebd695e11d327d16e2afcd8449c6c1e9f88 Reviewed-on: https://gerrit.chromium.org/gerrit/42432 Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
2c6696426c57941c1b37331b28fb594e2a0beab7 |
|
15-Jan-2013 |
beeps <beeps@chromium.org> |
[autotest] Docstring checker for pylint. Checks: 1. Non existant doc strings. 2. Empty docstrings. 3. Missing @param for each argument in method/function signature. 4. Does not check __init__, __del__ etc 5. Does check main, file, class, method,function. TEST=Created files with bad doc strings and tried repo upload. BUG=chromium-os:36895 Change-Id: I4742968f6648f164e45fb9ec19e20923901634f0 Reviewed-on: https://gerrit.chromium.org/gerrit/39372 Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
5553256ffaaa15b1bcaf92d58c14c06243c609fc |
|
16-Jan-2013 |
beeps <beeps@chromium.org> |
[autotest] Disable 'F' in pylint. Pylints import directory resolution model isn't the same as the python interpreters, so at times it believes it cannot import a module when the interpreter can. This failure is falky and depends on the path ordering/environment; it doesn't repro on my machine. Disabling the F mode for now. BUG=chromium-os:37948 TEST=Made sure it worked in the environment it failed in. Change-Id: I3a5f91a066d9e45d1db82135213675c109c3420a Reviewed-on: https://gerrit.chromium.org/gerrit/41429 Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
48fc6f50b87baa1ca6926c013e50b433f92d7aae |
|
07-Jan-2013 |
beeps <beeps@chromium.org> |
Enables pylint for .py files in autotest. 1. Patch run_pylint so pylint understands autotest_lib imports. 2. Patches pylint to understand 'import common' An unused improt error is only thrown if we don't see an autotest_lib import in the same scope. 3. Refactors run_pylint to handle command line invocation with multiple arguments correctly. 4. Adds a presubmit hook so we run pylint for autotest checkis. 5. Adds a pylintrc file, which only checks unused imports for now. Edit: Patches pylint to completely ignore import common. Currently, pylint only ignores 'import common' if it finds an autotest_lib in the same scope. This change patches pylint to completely ignore 'import common' regardless of autotest_lib. Sometimes the 'from' imports are parsed ahead of the regular imports, a more thorough understanding of when this happens is necessary before we can make pylint smarter. TEST=ran run_pylint on all python files in site_utils/ BUG=chromium-os:37650 Change-Id: Idf0d93f7a068c5d99b378f224e46ff6e524b4d0a Reviewed-on: https://gerrit.chromium.org/gerrit/40554 Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
40f4744243db135888488d22d14277b739f4acf8 |
|
07-Jan-2013 |
Alex Miller <milleral@chromium.org> |
Revert "Enables pylint for .py files in autotest." Handling of |import common| appears to be broken, and thus is breaking ability to upload any autotest code. This reverts commit 78ece92fc08f20e9d4f66c22b0bf034fe85ce9c2 Change-Id: I2522ece367b4d7eacd01fbea6ed9b0904fa16352 Reviewed-on: https://gerrit.chromium.org/gerrit/40532 Commit-Queue: Alex Miller <milleral@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> Tested-by: Alex Miller <milleral@chromium.org>
/external/autotest/utils/run_pylint.py
|
78ece92fc08f20e9d4f66c22b0bf034fe85ce9c2 |
|
04-Dec-2012 |
beeps <beeps@chromium.org> |
Enables pylint for .py files in autotest. 1. Patch run_pylint so pylint understands autotest_lib imports. 2. Patches pylint to understand 'import common' An unused improt error is only thrown if we don't see an autotest_lib import in the same scope. 3. Refactors run_pylint to handle command line invocation with multiple arguments correctly. 4. Adds a presubmit hook so we run pylint for autotest checkis. 5. Adds a pylintrc file, which only checks unused imports for now. TEST=ran run_pylint on all python files in client/ BUG=chromium-os:36890 Change-Id: Ic7b36c02474a454d1e5d254a3b21313fd2d8c745 Reviewed-on: https://gerrit.chromium.org/gerrit/39200 Reviewed-by: Scott Zawalski <scottz@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/run_pylint.py
|
8adf78936c915df6fd1edb6c592f40a7ed8350a5 |
|
09-Sep-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Autotest upstream merge. Merged from d9d64b855363d214996b187380532d4cc9991d29 to 7bad38846fe9c74e42018131ce85aec2b5e6c7a9 BUG=none TEST=emerge autotest, run bvt, smoke. Change-Id: Ibe6462198e84e0d41fa160af086283cd712da4a6 Reviewed-on: http://gerrit.chromium.org/gerrit/7440 Tested-by: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/utils/run_pylint.py
|
861b2d54aec24228cdb3895dbc40062cb40cb2ad |
|
04-Feb-2011 |
Eric Li <ericli@chromium.org> |
Merge remote branch 'cros/upstream' into master Merged to upstream autotest @4749~@5215. The entire change list description is too big to enlist here. Please refer to upstream (http://autotest.kernel.org/browser) for more details. BUG= TEST=emerged both x86 and arm build. Tested emerged x86 build bvt against a chromeos device. Review URL: http://codereview.chromium.org/6246035 Change-Id: I8455f2135c87c321c6efc232e2869dc8f675395e
/external/autotest/utils/run_pylint.py
|
bdaab795cffa33f9a37995bb283047cb03699272 |
|
07-Jan-2011 |
Kenneth Waters <kwaters@chromium.org> |
Revert "Merge remote branch 'cros/upstream' into autotest-rebase" This reverts commit 7edb30498d75a29a3287fe07070f2b51a116c5d4. TEST=Built for tegra2_seaboard BUG=10756 Review URL: http://codereview.chromium.org/6124004 Change-Id: Ifcd1a2279f5a62b99552a8f961c1430889a3a928
/external/autotest/utils/run_pylint.py
|
7edb30498d75a29a3287fe07070f2b51a116c5d4 |
|
07-Jan-2011 |
Eric Li <ericli@chromium.org> |
Merge remote branch 'cros/upstream' into autotest-rebase Merged to upstream trunk@5066, from trunk@4749. There is no way I could enlist each individual CL from the upstream here since it will blow up the changelist description field. BUG= TEST= Had patched this CL into a fresh cut client to avoid any side effect. run_remote_test bvt from both emerged location and third_party/autotest/file. Both test passed! We should also keep any eye on this to see how it gets propagated into cautotest server. TBR=dalecurtis Change-Id: I72f2bc7a9de530178484aea1bfb5ace68bcad029
/external/autotest/utils/run_pylint.py
|
2d6decca65786d43989cff1b284e925bab482bc6 |
|
02-Dec-2009 |
lmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4> |
Disable E1101/E1103 "Instace of ... has no ... member" in run_pylint Disable E1101/E1103 "Instace of ... has no ... member" in run_pylint. There are too many false positives. Signed-off-by: Steve Howard <showard@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3984 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/run_pylint.py
|
31476ebc9db64650728fd148daba1858fda8b6eb |
|
22-Nov-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Make run_pylint executable Signed-off-by: Martin J. Bligh <mbligh@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2492 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/run_pylint.py
|
65e06b1f47e07a73ee5bf3f9ace0cc3a9d859dd3 |
|
22-Aug-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
heck for pylint and print a more useful error message if it can't be imported, hinting that it needs to be installed. Risk: Low Visibility: run_pylint.py gives a more helpful error if pylint is not installed. Signed-off-by: John Admanski <jadmanski@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2028 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/run_pylint.py
|
94a6493803ec2e113c96677dda995603dac4863a |
|
22-Jul-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix up the run_pylint script to better understand the autotest_lib.* importing mechanism...its lack of understanding was leading to a lot of false positivies when trying to run pylint on our test files. Risk: Low Visibility: No more E0201 noise when running the script on test implementations. Signed-off-by: John Admanski <jadmanski@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@1878 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/run_pylint.py
|
b9083034743ad00f75f550eaa672eea87e603a21 |
|
25-Jun-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Moving the pylint running into a utils directory. Signed-off-by: Scott Zawalski <scottz@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@1739 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/run_pylint.py
|