Browse Source

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>
tags/2018.12.0
Al Bailey 2 years ago
parent
commit
4a248bfafd
2 changed files with 2 additions and 2 deletions
  1. +1
    -1
      base/setup/files/custom.sh
  2. +1
    -1
      tox.ini

+ 1
- 1
base/setup/files/custom.sh View File

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

+ 1
- 1
tox.ini View File

@@ -27,7 +27,7 @@ commands =
-not -name \*~ \
-not -name \*.md \
-name \*.sh \
-print0 | xargs -0 bashate -v \
-print0 | xargs -n 1 -0 bashate -v \
-i E006,E041,E042,E043,E044 -e E*"
bash -c "find {toxinidir} \
\( -path {toxinidir}/.tox \) -a -prune \


Loading…
Cancel
Save