From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/3] tst_test.sh: Call cleanup function after test start
Date: Thu, 7 Jan 2021 12:02:26 +0100 [thread overview]
Message-ID: <X/bqQinLuCM4xlId@pevik> (raw)
In-Reply-To: <X/bc+ZGQ6JPsg4YY@yuki.lan>
Hi Cyril,
> Hi!
> > It does not make sense to run the test cleanup function when the setup
> > function has been run.
> Did you mean "setup function hasn't been run." here?
> As it is this sentence does not make any sense to me.
Yes, thanks!
> > And at least some network tests expect setup has been run before running
> > cleanup (e.g. tcp_fastopen_run.sh).
> > When shell API was introduced, cleanup function was run only if 1) setup
> > function was defined 2) and also run. That was inconsistent from C API,
> > thus e7dc14caa run it always.
> > But shell API is different from C API: tst_brk can be called from
> > tst_test.sh (or other library which is run before tst_run, e.g.
> > tst_net.sh). That was probably the reason, why detection via
> > $TST_SETUP_STARTED was introduced in initial shell API.
> > NOTE: using type is better than grep $TST_TEST_PATH, because cleanup
> > function can be in other library sourced by the test.
> > Fixes: e7dc14caa ("tst_test.sh: Run cleanup even setup is not defined")
> This still possibly break tests that would call tst_brk() in the middle
> of setup and expect the cleanup() to be executed, right?
> I guess that we would need TST_DO_CLEANUP that would be set in both
> cases i.e. before we run setup and also before we execute the tests.
> What about this:
Good catch, agree.
I'm going to merge with one runtime fix:
> - if [ -n $TST_DO_CLEANUP -a -n "$TST_CLEANUP" -a -z "$TST_NO_CLEANUP" ]; then
> + if [ -n "$TST_DO_CLEANUP" -a -n "$TST_CLEANUP" -a -z "$TST_NO_CLEANUP" ]; then
Quotes are required otherwise we can get error:
/opt/ltp/testcases/bin/tst_test.sh: line 31: [: too many arguments
Kind regards,
Petr
> diff --git a/testcases/lib/tst_test.sh b/testcases/lib/tst_test.sh
> index 2417da140..94d95df6f 100644
> --- a/testcases/lib/tst_test.sh
> +++ b/testcases/lib/tst_test.sh
> @@ -28,7 +28,7 @@ _tst_do_exit()
> local ret=0
> TST_DO_EXIT=1
> - if [ -n "$TST_CLEANUP" -a -z "$TST_NO_CLEANUP" ]; then
> + if [ -n $TST_DO_CLEANUP -a -n "$TST_CLEANUP" -a -z "$TST_NO_CLEANUP" ]; then
> $TST_CLEANUP
> fi
> @@ -582,6 +582,7 @@ tst_run()
> [ -n "$TST_NEEDS_MODULE" ] && tst_require_module "$TST_NEEDS_MODULE"
> if [ -n "$TST_SETUP" ]; then
> + TST_DO_CLEANUP=1
> $TST_SETUP
> fi
> @@ -608,6 +609,7 @@ _tst_run_tests()
> local _tst_data="$1"
> local _tst_i
> + TST_DO_CLEANUP=1
> for _tst_i in $(seq ${TST_CNT:-1}); do
> if type ${TST_TESTFUNC}1 > /dev/null 2>&1; then
> _tst_run_test "$TST_TESTFUNC$_tst_i" $_tst_i "$_tst_data"
next prev parent reply other threads:[~2021-01-07 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 14:44 [LTP] [PATCH v4 0/3] shell API setup/cleanup checks Petr Vorel
2020-12-17 14:44 ` [LTP] [PATCH v4 1/3] tst_test.sh: Call cleanup function after test start Petr Vorel
2021-01-07 10:05 ` Cyril Hrubis
2021-01-07 11:02 ` Petr Vorel [this message]
2021-01-07 11:32 ` Petr Vorel
2020-12-17 14:44 ` [LTP] [PATCH v4 2/3] tst_test.sh: Warn on missing cleanup function Petr Vorel
2021-01-07 10:06 ` Cyril Hrubis
2020-12-17 14:44 ` [LTP] [PATCH v4 3/3] tst_test.sh: Exit when setup declared but not defined Petr Vorel
2021-01-07 10:07 ` Cyril Hrubis
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=X/bqQinLuCM4xlId@pevik \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox