From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] network: load test_net.sh after getopts
Date: Wed, 9 Nov 2016 14:26:38 +0300 [thread overview]
Message-ID: <582307EE.5060401@oracle.com> (raw)
In-Reply-To: <20161107121952.24933-1-pvorel@suse.cz>
Hi,
On 11/07/2016 03:19 PM, Petr Vorel wrote:
> We shouldn't ask rsh/ssh password or require having set ssh pub keys
> just for displaying help.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> testscripts/network.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/testscripts/network.sh b/testscripts/network.sh
> index 66bacef..fea2f68 100755
> --- a/testscripts/network.sh
> +++ b/testscripts/network.sh
> @@ -11,8 +11,6 @@ if [ $? -eq 0 ]; then
> export LTPROOT=${PWD}
> fi
>
> -. test_net.sh
> -
> export TMPDIR=/tmp/netpan-$$
> mkdir -p $TMPDIR
> CMDFILE=${TMPDIR}/network.tests
> @@ -81,6 +79,8 @@ if [ "$OPTIND" -eq 1 ]; then
> exit 1
> fi
>
> +. test_net.sh
> +
Agree, but we should reset TCID and TST_TOTAL after test_net.sh
inclusion (not before).
May be something like this where they were moved close to each other:
@@ -81,6 +79,8 @@ if [ "$OPTIND" -eq 1 ]; then
exit 1
fi
+TST_TOTAL=1
+TCID="network_settings"
+
+. test_net.sh
+
+# Reset variables.
+# Don't break the tests which are using 'testcases/lib/cmdlib.sh'
+export TCID=
+export TST_LIB_LOADED=
+
rm -f $CMDFILE
Best regards,
Alexey
> rm -f $CMDFILE
>
> for t in $TEST_CASES; do
next prev parent reply other threads:[~2016-11-09 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 12:19 [LTP] [PATCH 1/1] network: load test_net.sh after getopts Petr Vorel
2016-11-09 11:26 ` Alexey Kodanev [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-09 14:35 Petr Vorel
2016-11-11 8:58 ` Alexey Kodanev
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=582307EE.5060401@oracle.com \
--to=alexey.kodanev@oracle.com \
--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.