All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehee <jhpark1013@gmail.com>
To: Outreachy Linux Kernel <outreachy@lists.linux.dev>,
	Julia Denham <jdenham@redhat.com>,
	 Roopa Prabhu <roopa.prabhu@gmail.com>,
	Stefano Brivio <sbrivio@redhat.com>,
	netdev@vger.kernel.org,  Jaehee Park <jhpark1013@gmail.com>
Subject: Re: [PATCH net-next] selftests: net: vrf_strict_mode_test: add support to select a test to run
Date: Wed, 20 Apr 2022 01:01:16 -0400	[thread overview]
Message-ID: <CAA1TwFDXYFm4HaTuka_0ZcdD0BENwbCAGDKF44=_wpP3nTiWpg@mail.gmail.com> (raw)
In-Reply-To: <20220420045512.GA1289782@jaehee-ThinkPad-X1-Extreme>

Sorry, I sent two of the same patch by accident. Please ignore this one.


On Wed, Apr 20, 2022 at 12:55 AM Jaehee Park <jhpark1013@gmail.com> wrote:
>
> Add a boilerplate test loop to run all tests in
> vrf_strict_mode_test.sh.
>
> Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
> ---
>  .../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
> --
> 2.25.1
>

  reply	other threads:[~2022-04-20  5:01 UTC|newest]

Thread overview: 7+ 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 [this message]
2022-04-21 14:52 ` Roopa Prabhu
     [not found]   ` <ea64041b-635b-8c71-c9ac-b158403a276e@nvidia.com>
2022-04-21 15:05     ` Fwd: " Roopa Prabhu
2022-04-21 16:47   ` Jaehee Park
  -- 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='CAA1TwFDXYFm4HaTuka_0ZcdD0BENwbCAGDKF44=_wpP3nTiWpg@mail.gmail.com' \
    --to=jhpark1013@gmail.com \
    --cc=jdenham@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=outreachy@lists.linux.dev \
    --cc=roopa.prabhu@gmail.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 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.