From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 4/4] generate_lvm_runfile.sh: Fix bashism
Date: Mon, 8 Aug 2022 12:10:19 +0200 [thread overview]
Message-ID: <20220808101019.29892-5-pvorel@suse.cz> (raw)
In-Reply-To: <20220808101019.29892-1-pvorel@suse.cz>
ERR is not on dash (tested on 0.5.11).
using -e (i.e. implying 'set -e') is required to exit on any non zero
exit code. It requires 2 previous fixes.
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
testcases/misc/lvm/generate_lvm_runfile.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/testcases/misc/lvm/generate_lvm_runfile.sh b/testcases/misc/lvm/generate_lvm_runfile.sh
index 72b286a69..aba706c64 100755
--- a/testcases/misc/lvm/generate_lvm_runfile.sh
+++ b/testcases/misc/lvm/generate_lvm_runfile.sh
@@ -1,6 +1,7 @@
-#!/bin/sh
+#!/bin/sh -e
# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (c) 2020 SUSE LLC <mdoucha@suse.cz>
+# Copyright (c) Linux Test Project, 2022
#
# Generate LTP runfile for LVM tests (runtest/lvm.local)
@@ -13,7 +14,7 @@ LVM_TMPDIR="$LVM_DIR/ltp/growfiles"
generate_runfile()
{
- trap 'tst_brk TBROK "Cannot create LVM runfile"' ERR
+ trap '[ $? -eq 0 ] || tst_brk TBROK "Cannot create LVM runfile"' EXIT
INFILE="$LTPROOT/testcases/data/lvm/runfile.tpl"
OUTFILE="$LTPROOT/runtest/lvm.local"
FS_LIST=`tst_supported_fs`
--
2.37.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-08-08 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 10:10 [LTP] [PATCH v3 0/4] set -e and bashism fixes Petr Vorel
2022-08-08 10:10 ` [LTP] [PATCH v3 1/4] tst_test.sh: runtest.sh: Remove unused code Petr Vorel
2022-08-08 10:10 ` [LTP] [PATCH v3 2/4] tst_ansi_color.sh: Allow to run with set -e Petr Vorel
2022-08-08 11:12 ` Petr Vorel
2022-08-08 10:10 ` [LTP] [PATCH v3 3/4] tst_test.sh: Fix _tst_cleanup_timer() on " Petr Vorel
2022-08-08 10:10 ` Petr Vorel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220808101019.29892-5-pvorel@suse.cz \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.