From: Jaehee Park <jhpark1013@gmail.com>
To: Roopa Prabhu <roopa@nvidia.com>
Cc: outreachy@lists.linux.dev, Julia Denham <jdenham@redhat.com>,
Roopa Prabhu <roopa.prabhu@gmail.com>,
Stefano Brivio <sbrivio@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: net: vrf_strict_mode_test: add support to select a test to run
Date: Thu, 21 Apr 2022 12:47:31 -0400 [thread overview]
Message-ID: <20220421164731.GA3485444@jaehee-ThinkPad-X1-Extreme> (raw)
In-Reply-To: <41a48002-817b-4366-d316-9d94e8d81a79@nvidia.com>
On Thu, Apr 21, 2022 at 07:52:45AM -0700, Roopa Prabhu wrote:
>
> On 4/19/22 21:55, Jaehee Park wrote:
> > Add a boilerplate test loop to run all tests in
> > vrf_strict_mode_test.sh.
> >
> > Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
> > ---
>
> Jaehee, this needs more work. The idea is to be able to run individual tests
> with -t option.
>
> An example is drop_monitor_tests.sh, see the usage and getopts arg parsing
> at the beginning of the test
>
> eg ./drop_monitor_tests.sh -t <testname>
>
>
Thanks Roopa, I've sent version 2 for your review.
> > .../testing/selftests/net/vrf_strict_mode_test.sh | 14 +++++++++++++-
> > 1 file changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/net/vrf_strict_mode_test.sh b/tools/testing/selftests/net/vrf_strict_mode_test.sh
> > index 865d53c1781c..116ca43381b5 100755
> > --- a/tools/testing/selftests/net/vrf_strict_mode_test.sh
> > +++ b/tools/testing/selftests/net/vrf_strict_mode_test.sh
> > @@ -14,6 +14,8 @@ INIT_NETNS_NAME="init"
> > PAUSE_ON_FAIL=${PAUSE_ON_FAIL:=no}
> > +TESTS="vrf_strict_mode_tests_init vrf_strict_mode_tests_testns vrf_strict_mode_tests_mix"
> > +
> > log_test()
> > {
> > local rc=$1
> > @@ -391,7 +393,17 @@ fi
> > cleanup &> /dev/null
> > setup
> > -vrf_strict_mode_tests
> > +for t in $TESTS
> > +do
> > + case $t in
> > + vrf_strict_mode_tests_init|vrf_strict_mode_init) vrf_strict_mode_tests_init;;
> > + vrf_strict_mode_tests_testns|vrf_strict_mode_testns) vrf_strict_mode_tests_testns;;
> > + vrf_strict_mode_tests_mix|vrf_strict_mode_mix) vrf_strict_mode_tests_mix;;
> > +
> > + help) echo "Test names: $TESTS"; exit 0;;
> > +
> > + esac
> > +done
> > cleanup
> > print_log_test_results
next prev parent reply other threads:[~2022-04-21 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 4:55 [PATCH net-next] selftests: net: vrf_strict_mode_test: add support to select a test to run Jaehee Park
2022-04-20 5:01 ` Jaehee
2022-04-21 14:52 ` Roopa Prabhu
2022-04-21 16:47 ` Jaehee Park [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 4:46 [PATCH] [net-next] " Jaehee Park
2022-04-21 14:53 ` Roopa Prabhu
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=20220421164731.GA3485444@jaehee-ThinkPad-X1-Extreme \
--to=jhpark1013@gmail.com \
--cc=jdenham@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=roopa.prabhu@gmail.com \
--cc=roopa@nvidia.com \
--cc=sbrivio@redhat.com \
/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