From 7f03322daca6a95144086cf3e9a70081089189c1 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Fri, 10 Nov 2023 09:19:17 -0500 Subject: [PATCH] run-in-py-utils-bt2-env.sh: use `[[ ... ]]` instead of `[` or `test` For the same reason we're using this form in `utils.sh` (see "tests/utils/utils.sh: use `[[ ... ]]` instead of `[` or `test`"). Signed-off-by: Philippe Proulx Change-Id: I9284cff1dc7d64cfbcf2ad56e6a3d2bd3652fb6e --- tests/utils/run-in-py-env.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/utils/run-in-py-env.sh b/tests/utils/run-in-py-env.sh index 6f197d73..86d5eeb2 100755 --- a/tests/utils/run-in-py-env.sh +++ b/tests/utils/run-in-py-env.sh @@ -5,7 +5,7 @@ # Copyright (C) 2017-2023 Philippe Proulx # Copyright (C) 2019 Simon Marchi -if [ -n "${BT_TESTS_SRCDIR:-}" ]; then +if [[ -n "${BT_TESTS_SRCDIR:-}" ]]; then UTILSSH="$BT_TESTS_SRCDIR/utils/utils.sh" else UTILSSH="$(dirname "$0")/../utils/utils.sh" @@ -25,13 +25,13 @@ usage() { echo "environment variable to the built \`tests\` directory." } -if [ -z "$*" ]; then +if [[ -z "$*" ]]; then usage exit 1 fi # Sanity check that the BT_TESTS_BUILDDIR value makes sense. -if [ ! -f "$BT_TESTS_BUILDDIR/Makefile" ]; then +if [[ ! -f "$BT_TESTS_BUILDDIR/Makefile" ]]; then fold -w 80 -s <<- END $0: BT_TESTS_BUILDDIR does not point to a valid directory (\`$BT_TESTS_BUILDDIR/Makefile\` does not exist). -- 2.34.1