From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net] selftests: mptcp: fix MP_FAIL test-case
Date: Tue, 3 May 2022 11:39:43 -0700 (PDT) [thread overview]
Message-ID: <ec75c84-1e92-3a7a-3c92-d64f40d37e69@linux.intel.com> (raw)
In-Reply-To: <66bebfa5f6fcfc6180e13861bd1f629b066a5f4d.camel@redhat.com>
On Tue, 3 May 2022, Paolo Abeni wrote:
> Hello,
>
> On Fri, 2022-04-29 at 12:46 -0700, Mat Martineau wrote:
>> On Fri, 29 Apr 2022, Paolo Abeni wrote:
>>
>>> The mentioned tests sometimes fails because the data
>>> transfer completes before any packet is sent on the 2nd
>>> link (the failing one).
>>>
>>> Address the issue reducing the "virtual" b/w available
>>> on the primary link.
>>>
>>> Fixes: bfd4cdbe7032 ("selftests: mptcp: add MP_FAIL reset testcase")
>>> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>>> ---
>>> together with the previous patch this fixes issues/265 for
>>> good here. I'm not adding the Close tag due to the mentioned
>>> dep, which may take a different/longer route
>>> ---
>>> tools/testing/selftests/net/mptcp/mptcp_join.sh | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
>>> index a98fee834950..0d65295c1b33 100755
>>> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
>>> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
>>> @@ -2734,7 +2734,7 @@ fail_tests()
>>>
>>> # multiple subflows
>>> if reset_with_fail "MP_FAIL MP_RST" 2; then
>>> - tc -n $ns2 qdisc add dev ns2eth1 root netem rate 20mbit delay 1
>>> + tc -n $ns2 qdisc add dev ns2eth1 root netem rate 10mbit delay 5
>>
>> The "MP_FAIL MP_RST" test still fails within a couple of minutes on my
>> desktop with this change. I changed 10mbit to 1mbit and so far it is still
>> running. You ok with slowing it down even more?
>
> [sorry I almost missed this comment]. Just to be sure, is such test
> running on top of the pedit patch? (we need both of them). Otherwise no
> objection to reduce the rate even more.
>
Yes, I was testing with both patches applied.
--
Mat Martineau
Intel
prev parent reply other threads:[~2022-05-03 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 16:04 [PATCH mptcp-net] selftests: mptcp: fix MP_FAIL test-case Paolo Abeni
2022-04-29 17:34 ` Mat Martineau
2022-04-29 17:47 ` selftests: mptcp: fix MP_FAIL test-case: Tests Results MPTCP CI
2022-04-29 19:46 ` [PATCH mptcp-net] selftests: mptcp: fix MP_FAIL test-case Mat Martineau
2022-05-03 17:06 ` Paolo Abeni
2022-05-03 18:39 ` Mat Martineau [this message]
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=ec75c84-1e92-3a7a-3c92-d64f40d37e69@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox