From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v6 3/7] network.sh: Migrate to new shell API
Date: Tue, 10 Apr 2018 15:37:28 +0300 [thread overview]
Message-ID: <fcdbaf75-7003-ff02-4fb6-6acfc0b504a2@oracle.com> (raw)
In-Reply-To: <20180406123118.21309-4-pvorel@suse.cz>
On 04/06/2018 03:31 PM, Petr Vorel wrote:
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> testscripts/network.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testscripts/network.sh b/testscripts/network.sh
> index cc2b2de72..b18f202d5 100755
> --- a/testscripts/network.sh
> +++ b/testscripts/network.sh
> @@ -89,7 +89,7 @@ shift $(($OPTIND - 1))
> TST_TOTAL=1
> TCID="network_settings"
Do we need these variables in the new API?
For TCID, I guess we would also need this change in tst_test.sh:
diff --git a/testcases/lib/tst_test.sh b/testcases/lib/tst_test.sh
index 6c2ee6a..b7aa4a7 100644
--- a/testcases/lib/tst_test.sh
+++ b/testcases/lib/tst_test.sh
@@ -102,7 +102,7 @@ tst_res()
tst_inc_res "$res"
- printf "$TCID $TST_COUNT "
+ printf "$TST_ID $TST_COUNT "
tst_print_colored $res "$res: "
echo "$@"
}
Thanks,
Alexey
>
> -TST_USE_LEGACY_API=1
> +TST_NO_DEFAULT_RUN=1
> . tst_net.sh
>
> # Reset variables.
>
next prev parent reply other threads:[~2018-04-10 12:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 12:31 [LTP] [RFC PATCH v6 0/7] Rewriting network tests into new shell API Petr Vorel
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 1/7] tst_net.sh: Support both new and legacy APIs + rename Petr Vorel
2018-05-03 9:19 ` Xiao Yang
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 2/7] tst_test.sh: Introduce TST_NO_DEFAULT_RUN Petr Vorel
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 3/7] network.sh: Migrate to new shell API Petr Vorel
2018-04-08 20:47 ` Petr Vorel
2018-04-10 12:37 ` Alexey Kodanev [this message]
2018-04-10 17:00 ` Petr Vorel
2018-04-11 9:29 ` Alexey Kodanev
2018-04-11 11:02 ` Petr Vorel
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 4/7] network/interface: Cleanup if4-addr-change Petr Vorel
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 5/7] network/if-updown: Restore IP in cleanup function Petr Vorel
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 6/7] tst_net_stress.sh: Migrate with dependencies to new API + rename Petr Vorel
2018-04-10 12:58 ` Alexey Kodanev
2018-04-10 17:37 ` Petr Vorel
2018-04-11 9:08 ` Alexey Kodanev
2018-04-11 9:45 ` Petr Vorel
2018-04-06 12:31 ` [LTP] [RFC PATCH v6 7/7] network/interface: Split tests to test only one command per test Petr Vorel
2018-04-10 11:21 ` [LTP] [RFC PATCH v6 0/7] Rewriting network tests into new shell API Alexey Kodanev
2018-04-10 15:18 ` Petr Vorel
2018-04-10 13:45 ` Petr Vorel
2018-04-10 17:41 ` Petr Vorel
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=fcdbaf75-7003-ff02-4fb6-6acfc0b504a2@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.