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.
Reviewed: https:/ /review. opendev. org/744712 /git.openstack. org/cgit/ starlingx/ config/ commit/ ?id=fc8b109ef05 98534f1f137ee3d 259cef396bfa03
Committed: https:/
Submitter: Zuul
Branch: master
commit fc8b109ef059853 4f1f137ee3d259c ef396bfa03
Author: albailey <email address hidden>
Date: Tue Aug 4 08:45:26 2020 -0500
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: I7587b7017b6855 aad63dfaeaea5ec ca0bcfc21ea
Closes-Bug: 1890287
Signed-off-by: albailey <email address hidden>