From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net 0/2] selftests: mptcp: join: longer timeout
Date: Mon, 17 Nov 2025 12:08:23 +0100 [thread overview]
Message-ID: <8aeea045-c68d-493a-8f83-4a9187480428@kernel.org> (raw)
In-Reply-To: <20251112-slft-longer-timeout-v1-0-97aab145a062@kernel.org>
Hello,
On 12/11/2025 10:45, Matthieu Baerts (NGI0) wrote:
> A previous attempt was helping, but not enough as the background
> connections were still stopped after the timeout. That's what the MPTCP
> CI recently reported with the "delete and re-add" subtest taking a bit
> more than one minute in a debug environment.
>
> To play it safe, and because increasing the timeout for the background
> connections doesn't change anything to the end result (the transfer is
> not checked in this case), all subtests with a background connection not
> waiting for it to end now have a longer timeout.
I hope it is OK if I apply these patches now: they are simple, linked to
recent patches, and we still have quite a few patches in the queue.
I'm planning to send them with other patches we have in the queue for
net ideally today.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-11-17 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 9:45 [PATCH mptcp-net 0/2] selftests: mptcp: join: longer timeout Matthieu Baerts (NGI0)
2025-11-12 9:45 ` [PATCH mptcp-net 1/2] selftests: mptcp: join: endpoints: " Matthieu Baerts (NGI0)
2025-11-12 9:45 ` [PATCH mptcp-net 2/2] selftests: mptcp: join: userspace: " Matthieu Baerts (NGI0)
2025-11-12 11:13 ` [PATCH mptcp-net 0/2] selftests: mptcp: join: " MPTCP CI
2025-11-17 11:08 ` Matthieu Baerts [this message]
2025-11-17 11:26 ` Matthieu Baerts
2025-11-18 8:43 ` Geliang Tang
2025-11-18 16:06 ` 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=8aeea045-c68d-493a-8f83-4a9187480428@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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