starlingx/integ
Code Issues Proposed changes

Bashate was not detecting E004 in all cases

Browse Source 
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:
Al Bailey 2018-10-31 09:55:18 -05:00
parent 6a6ea416e1
commit 4a248bfafd
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
base/setup/files/custom.sh
View File

@ -1 +1 @@
export TMOUT=900 export TMOUT=900

2
tox.ini
View File

@ -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 \