Bashate was not detecting E004 in all cases
Bashate was not always detecting: E004 File did not end with a newline unless the last file processed by bashate had the violation. This meant that zuul jobs would randomly fail. The fix is run individually (-n 1) Change-Id: I7934c3da82adb450fd1ba5f2630591369df8b828 Closes-Bug: 1800865 Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
This commit is contained in:
parent
6a6ea416e1
commit
4a248bfafd
2
tox.ini
2
tox.ini
@ -27,7 +27,7 @@ commands =
|
|||||||
-not -name \*~ \
|
-not -name \*~ \
|
||||||
-not -name \*.md \
|
-not -name \*.md \
|
||||||
-name \*.sh \
|
-name \*.sh \
|
||||||
-print0 | xargs -0 bashate -v \
|
-print0 | xargs -n 1 -0 bashate -v \
|
||||||
-i E006,E041,E042,E043,E044 -e E*"
|
-i E006,E041,E042,E043,E044 -e E*"
|
||||||
bash -c "find {toxinidir} \
|
bash -c "find {toxinidir} \
|
||||||
\( -path {toxinidir}/.tox \) -a -prune \
|
\( -path {toxinidir}/.tox \) -a -prune \
|
||||||
|
Loading…
Reference in New Issue
Block a user