run_tests.sh was created as an entry point for bashate. We stopped
using it now that we know how to run bashate directly in the gate.
We lost running an unrelated bashate test when that happened.
Devstack does have unit tests. We don't run them. We should.
Especially when working on things like the LIBS_FROM_GIT which is
sufficiently tricky that we really need to add unit tests to ensure
that we don't break it.
Change-Id: Ife067855569e2eae4c085471d326e8086de37332
The addition of the crazy-refs check masked the bash8 exit code. So add
the same pass/fail handling from exercise.sh to provide a neat summary at
the end of the run.
Change-Id: I169eb90c619a114cf8584bee70b7dcda67769dc5
as found by dansmith's clever hack, if devstack lands a crazy
branch name in stackrc, we'd break the devstack gate. While it's
doubtful anyone would do this, add a basic sanity check.
Change-Id: Ib3b1881ed4fd520a1828ed073a7c8353e6f0a839
this gives a simple way to run against all the files that we'd
want to check with bash8. Currently clocking in at 300+ errors
(no false pos so far that I see).
Change-Id: Idd83b0bf61029b49bb28ad8b6e6261ecbf927555
Ian Wienand