From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v16 0/8] userspace pm remove id 0 subflow & address
Date: Fri, 13 Oct 2023 19:30:06 +0800 [thread overview]
Message-ID: <20231013113006.GA29962@bogon> (raw)
In-Reply-To: <b783f33b-ae88-4509-9b9e-53736fd4dd5a@kernel.org>
On Fri, Oct 13, 2023 at 11:36:36AM +0200, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 13/10/2023 10:31, Matthieu Baerts wrote:
> > Hi Geliang, Paolo,
> >
> > On 13/10/2023 07:46, Geliang Tang wrote:
> >> v16:
> >> - address Matt's comments in v15.
> >
> > Thank you for the new version! It looks good to me!
> >
> > Reviewed-by: Matthieu Baerts <matttbe@kernel.org>
>
> Mmh, I missed the errors reported by the CI:
>
> not ok 112 - mptcp_join: userspace pm add & remove address
> not ok 113 - mptcp_join: userspace pm create destroy subflow
> not ok 115 - mptcp_join: userspace pm remove initial subflow
> not ok 116 - mptcp_join: userspace pm send RM_ADDR for ID 0
>
> Do you mind looking at that, please?
I can't reproduce these errors. All tests passed on my side.
I run this command on my Thinkpad laptop:
docker run \
-e INPUT_BUILD_SKIP_PERF=1 \
-e INPUT_BUILD_SKIP_PACKETDRILL=1 \
-v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
--pull always mptcp/mptcp-upstream-virtme-docker:latest \
auto-debug
And this is my .virtme-exec-run:
run_selftest_one ./mptcp_join.sh -u
Every tests passed.
Is there a difference between my test environment and CI?
Thanks,
-Geliang
>
> I wonder if I should not revert some patches (for the moment) or disable
> some checks: these errors are visible on other builds, and we are
> missing real issues.
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
next prev parent reply other threads:[~2023-10-13 11:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 5:46 [PATCH mptcp-next v16 0/8] userspace pm remove id 0 subflow & address Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 1/8] mptcp: add __mptcp_subflow_disconnect helper Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 2/8] selftests: mptcp: join: no RST when rm subflow/addr Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 3/8] Squash to "mptcp: add mptcpi_subflows_total counter" Geliang Tang
2023-10-13 10:32 ` Paolo Abeni
2023-10-13 10:46 ` Matthieu Baerts
2023-10-13 15:35 ` Paolo Abeni
2023-10-16 11:53 ` Matthieu Baerts
2023-10-16 13:50 ` Paolo Abeni
2023-10-16 20:26 ` Matthieu Baerts
2023-10-13 5:46 ` [PATCH mptcp-next v16 4/8] Squash to "selftests: mptcp: add chk_subflows_total helper" Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 5/8] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 6/8] mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 7/8] mptcp: userspace pm rename remove_err to out Geliang Tang
2023-10-13 5:46 ` [PATCH mptcp-next v16 8/8] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-13 6:57 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
2023-10-13 10:18 ` MPTCP CI
2023-10-13 8:31 ` [PATCH mptcp-next v16 0/8] userspace pm remove id 0 subflow & address Matthieu Baerts
2023-10-13 9:36 ` Matthieu Baerts
2023-10-13 11:30 ` Geliang Tang [this message]
2023-10-13 11:54 ` 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=20231013113006.GA29962@bogon \
--to=geliang.tang@suse.com \
--cc=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 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.