hack/verify-e2e-suites.sh: non-zero exit code when there were errors

The script correctly reported errors, but did not return a non-zero exit
code. Therefore errors would have been overlooked during pull-kubernetes-verify
runs.
This commit is contained in:
Patrick Ohly 2024-04-17 19:35:22 +02:00
parent 79c61d5f03
commit 0b5456c13b

View File

@ -31,6 +31,7 @@ cd "${KUBE_ROOT}"
kube::util::ensure-temp-dir
res=0
for suite in $(git grep -l framework.AfterReadingAllFlags | grep -v -e ^test/e2e/framework -e ^hack | xargs -n 1 dirname | sort -u); do
# Build a binary and run it in the root directory to get paths that are
# relative to that instead of the package directory.
@ -41,5 +42,7 @@ for suite in $(git grep -l framework.AfterReadingAllFlags | grep -v -e ^test/e2e
echo >&2 "ERROR: E2E test suite invocation failed for $suite."
# shellcheck disable=SC2001
echo "$out" | sed -e 's/^/ /'
res=1
fi
done
exit "$res"