MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 0/5] selftests: mptcp: more info in case of errors
Date: Sun, 12 Jan 2025 13:38:11 +0100	[thread overview]
Message-ID: <7c6de0fc-5af3-41f0-8ac1-b4816ab7575d@kernel.org> (raw)
In-Reply-To: <20250108-slft-mptcp-conn-misc-impr-v1-0-bdfbdba48a1f@kernel.org>

Hi Geliang,

On 08/01/2025 19:40, Matthieu Baerts (NGI0) wrote:
> Here are just a bunch of small improvements:
> 
> - MIB and 'ss -Me' in simult_flows.sh
> - move common code to lib.sh
> - use 'ss' with '-m'
> - remove unused variable
> - show only the size instead of size + filename
> 
> Nothing exiting, but the 3rd one can help investigating some issues like
> https://github.com/multipath-tcp/mptcp_net-next/issues/499

Now in our tree (feat. for net-next) with Geliang's RvB tag (I hope
that's OK),

New patches for t/upstream:
- 5731da7ccbbf: selftests: mptcp: simult_flows: unify errors msgs
- 668a6c97c2b1: selftests: mptcp: sockopt: save nstat infos
- 1cb853be929c: selftests: mptcp: move stats info in case of errors to
lib.sh
- a97277439285: selftests: mptcp: add -m with ss in case of errors
- 70019b947cf7: selftests: mptcp: connect: remove unused variable
- c94beebdce72: selftests: mptcp: connect: better display the files size
- Results: 17aabfa75062..632bb7330ffe (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/3d444e3a3d41f6228c9bcdc5dbf649cc6857c7d3/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      parent reply	other threads:[~2025-01-12 12:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 18:40 [PATCH mptcp-next 0/5] selftests: mptcp: more info in case of errors Matthieu Baerts (NGI0)
2025-01-08 18:40 ` [PATCH mptcp-next 1/5] selftests: mptcp: simult_flows: unify errors msgs Matthieu Baerts (NGI0)
2025-01-10  8:16   ` Geliang Tang
2025-01-10 10:35     ` Matthieu Baerts
2025-01-08 18:40 ` [PATCH mptcp-next 2/5] selftests: mptcp: move stats info in case of errors to lib.sh Matthieu Baerts (NGI0)
2025-01-09  9:24   ` Geliang Tang
2025-01-09 15:30     ` Matthieu Baerts
2025-01-10  3:05       ` Geliang Tang
2025-01-08 18:40 ` [PATCH mptcp-next 3/5] selftests: mptcp: add -m with ss in case of errors Matthieu Baerts (NGI0)
2025-01-08 18:40 ` [PATCH mptcp-next 4/5] selftests: mptcp: connect: remove unused variable Matthieu Baerts (NGI0)
2025-01-08 18:40 ` [PATCH mptcp-next 5/5] selftests: mptcp: connect: better display the files size Matthieu Baerts (NGI0)
2025-01-08 19:50 ` [PATCH mptcp-next 0/5] selftests: mptcp: more info in case of errors MPTCP CI
2025-01-12 12:38 ` Matthieu Baerts [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=7c6de0fc-5af3-41f0-8ac1-b4816ab7575d@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@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