From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>,
Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net] selftests: mptcp: gives slow test-case more time
Date: Mon, 24 Oct 2022 17:11:36 -0700 (PDT) [thread overview]
Message-ID: <690a5b2d-6bb6-9d28-e2dc-6841021aaa70@linux.intel.com> (raw)
In-Reply-To: <680973297b6995126f49732c0828ccfce8865c72.1666628806.git.pabeni@redhat.com>
On Mon, 24 Oct 2022, Paolo Abeni wrote:
> On slow or busy VM, some test-cases still fail because the
> data transfer completes before the endpoint manipulation
> actually took effect.
>
> Address the issue by artificially increasing the runtime for
> the relevant test-cases.
>
> Fixes: ef360019db40 ("selftests: mptcp: signal addresses testcases")
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/309
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> tools/testing/selftests/net/mptcp/mptcp_join.sh | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index f3dd5f2a0272..2eeaf4aca644 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -2152,7 +2152,7 @@ remove_tests()
> pm_nl_set_limits $ns2 1 3
> pm_nl_add_endpoint $ns2 10.0.3.2 flags subflow
> pm_nl_add_endpoint $ns2 10.0.4.2 flags subflow
> - run_tests $ns1 $ns2 10.0.1.1 0 -1 -2 slow
> + run_tests $ns1 $ns2 10.0.1.1 0 -1 -2 speed_10
> chk_join_nr 3 3 3
> chk_add_nr 1 1
> chk_rm_nr 2 2
> @@ -2165,7 +2165,7 @@ remove_tests()
> pm_nl_add_endpoint $ns1 10.0.3.1 flags signal
> pm_nl_add_endpoint $ns1 10.0.4.1 flags signal
> pm_nl_set_limits $ns2 3 3
> - run_tests $ns1 $ns2 10.0.1.1 0 -3 0 slow
> + run_tests $ns1 $ns2 10.0.1.1 0 -3 0 speed_10
> chk_join_nr 3 3 3
> chk_add_nr 3 3
> chk_rm_nr 3 3 invert
> @@ -2178,7 +2178,7 @@ remove_tests()
> pm_nl_add_endpoint $ns1 10.0.3.1 flags signal
> pm_nl_add_endpoint $ns1 10.0.14.1 flags signal
> pm_nl_set_limits $ns2 3 3
> - run_tests $ns1 $ns2 10.0.1.1 0 -3 0 slow
> + run_tests $ns1 $ns2 10.0.1.1 0 -3 0 speed_10
> chk_join_nr 1 1 1
> chk_add_nr 3 3
> chk_rm_nr 3 1 invert
> --
> 2.37.3
Looks good to me:
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Do you want me to get this in to the export branch soon, or should we
leave it queued for Matthieu?
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-10-25 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:27 [PATCH mptcp-net] selftests: mptcp: gives slow test-case more time Paolo Abeni
2022-10-24 18:33 ` selftests: mptcp: gives slow test-case more time: Tests Results MPTCP CI
2022-10-25 0:11 ` Mat Martineau [this message]
2022-10-25 2:39 ` MPTCP CI
2022-10-31 14:55 ` [PATCH mptcp-net] selftests: mptcp: gives slow test-case more time Matthieu Baerts
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=690a5b2d-6bb6-9d28-e2dc-6841021aaa70@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@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.