manila/tools
Luis Pabón 72d2840048 Enable developers to see pylint output
The program tools/lintstack.py which is executed by
tools/lintstack.sh when Jenkins runs, only tests for differences
in the output of pylint. Right now, there seems to be
17 errors/warnings that are being carried over from fix to fix,
with no difference between fixes, and so no failures in the
pylint Jenkins job.

It is really difficult to tell what the errors are, so this fix
allows developers determine what the errors are by running the
following command:

$ tox -e lint

A sample output of the command is available as an attachment
to the bug.

Change-Id: I88487829576d55d437b934e08571013b7a6e57cf
Signed-off-by: Luis Pabón <lpabon@redhat.com>
Closes-Bug: #1356588
Signed-off-by: Luis Pabón <lpabon@redhat.com>
2015-04-03 15:10:18 -04:00
..
colorizer.py Sync scripts with oslo-incubator 2014-08-14 12:09:46 +02:00
enable-pre-commit-hook.sh docs 2013-09-17 10:57:47 +03:00
install_venv_common.py Sync scripts with oslo-incubator 2014-08-14 12:09:46 +02:00
install_venv.py Sync with oslo-incubator 2014-10-26 08:12:04 +00:00
lintstack.py Enable developers to see pylint output 2015-04-03 15:10:18 -04:00
lintstack.sh Initialize from cinder 2013-08-08 10:34:06 -04:00
with_venv.sh Sync scripts with oslo-incubator 2014-08-14 12:09:46 +02:00