Browse Source

Fix a random tox linters failure in bashate

There was a file that was missing a newline which would
cause bashate to fail.
However the bashate command was being run as a list of inputs
rather than as individual files, so that error was being ignored
unless that bad file was the last file processed.
This submission fixes the file, and ensures that tox linters
job will fail is any file has an error, regardless of what is
processed afterwards.

Change-Id: I7587b7017b6855aad63dfaeaea5ecca0bcfc21ea
Closes-Bug: 1890287
Signed-off-by: albailey <Al.Bailey@windriver.com>
changes/12/744712/1
albailey 1 year ago
parent
commit
fc8b109ef0
  1. 2
      sysinv/sysinv/sysinv/scripts/validate-platform-backup.sh
  2. 2
      tox.ini

2
sysinv/sysinv/sysinv/scripts/validate-platform-backup.sh

@ -49,4 +49,4 @@ for part_number in "${part_numbers[@]}"; do
fi
done
log "Valid platform-backup partition not found"
exit 1
exit 1

2
tox.ini

@ -24,7 +24,7 @@ commands =
-not -name \*~ \
-not -name \*.md \
-name \*.sh \
-print0 | xargs -0 bashate -v -e E* \
-print0 | xargs -r -n 1 -0 bashate -v -e E* \
-i E006,E010"
bash -c "find {toxinidir} \

Loading…
Cancel
Save