From 1288bee3175d28785a59e83041bf13206829d58e Mon Sep 17 00:00:00 2001 From: Sevan Janiyan Date: Wed, 2 Jun 2021 14:55:53 -0400 Subject: [PATCH] testsuite/systemtap.base/perf.sh drop bashism You don't need to use == to check for equality in a test statement, a single equals sign is sufficient. The use of double equals sign is a bashism which doesn't always translate as intended on other shells. [fche checked other scripts in the source tree that used [ == ]; they are all marked /bin/bash so can stay as is.] --- testsuite/systemtap.base/perf.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testsuite/systemtap.base/perf.sh b/testsuite/systemtap.base/perf.sh index 9a0c79861..3081b72c5 100755 --- a/testsuite/systemtap.base/perf.sh +++ b/testsuite/systemtap.base/perf.sh @@ -56,7 +56,7 @@ probe end done -if [ "${perfresult['first']}" == "${perfresult['second']}" ] ; then +if [ "${perfresult['first']}" = "${perfresult['second']}" ] ; then echo PASS: ${perfresult["first"]} else echo UNRESOLVED: ${perfresult["first"]} ${perfresult["second"]} -- 2.43.5