From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net 3/3] selftests: mptcp: simult_flows: disable 'flaky' mark
Date: Mon, 18 May 2026 17:28:34 +1000 [thread overview]
Message-ID: <8a4c5085-7dd7-4a1c-920b-2eb228d45f74@kernel.org> (raw)
In-Reply-To: <20260508-mptcp-sft-sflows-bufferbloat-v1-3-e9b0d25d9789@kernel.org>
Hello,
On 08/05/2026 19:54, Matthieu Baerts (NGI0) wrote:
> Thanks to recent commits removing high bufferbloat in this case, the
> "unbalanced bwidth" subtest has a more stable transfer.
>
> Thanks to that, it looks like the test is no longer flaky (hopefully).
Too soon apparently: when validating something else, I managed to have
this "unbalanced bwidth" subtest failing again... I then reverted this
patch, keeping the flaky mark for the moment:
New patches for t/upstream:
- 584a6166fbf6: Revert "selftests: mptcp: simult_flows: disable 'flaky'
mark"
- Results: 0c8a93820ed7..23350e342bf2 (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/c2a7d8421fcddc899e9ebd250112c5a70be01aa0/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-05-18 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 17:54 [PATCH mptcp-net 0/3] selftests: mptcp: simult_flows: reduce bufferbloat Matthieu Baerts (NGI0)
2026-05-08 17:54 ` [PATCH mptcp-net 1/3] selftests: mptcp: simult_flows: disable GSO Matthieu Baerts (NGI0)
2026-05-08 17:54 ` [PATCH mptcp-net 2/3] selftests: mptcp: simult_flows: adapt limits Matthieu Baerts (NGI0)
2026-05-08 17:54 ` [PATCH mptcp-net 3/3] selftests: mptcp: simult_flows: disable 'flaky' mark Matthieu Baerts (NGI0)
2026-05-18 7:28 ` Matthieu Baerts [this message]
2026-05-08 18:54 ` [PATCH mptcp-net 0/3] selftests: mptcp: simult_flows: reduce bufferbloat MPTCP CI
2026-05-08 19:45 ` MPTCP CI
2026-05-08 20:49 ` MPTCP CI
2026-05-11 20:16 ` Mat Martineau
2026-05-12 8:46 ` 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=8a4c5085-7dd7-4a1c-920b-2eb228d45f74@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