MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v3 0/5] add mptcp_subflow bpf_iter
Date: Tue, 10 Sep 2024 06:30:50 +0000	[thread overview]
Message-ID: <9c607dc6-979f-f6b4-3473-ec717f1df763@gmail.com> (raw)
In-Reply-To: <cover.1725946276.git.tanggeliang@kylinos.cn>

Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal: Success! ✅
- KVM Validation: debug: Success! ✅
- KVM Validation: btf (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/10786552827

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/ed6d012aaff4
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=888713


If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:

    $ cd [kernel source code]
    $ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
        --pull always mptcp/mptcp-upstream-virtme-docker:latest \
        auto-normal

For more details:

    https://github.com/multipath-tcp/mptcp-upstream-virtme-docker


Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)

      parent reply	other threads:[~2024-09-10  6:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  5:37 [PATCH mptcp-next v3 0/5] add mptcp_subflow bpf_iter Geliang Tang
2024-09-10  5:37 ` [PATCH mptcp-next v3 1/5] bpf: Add " Geliang Tang
2024-09-11 21:00   ` Andrii Nakryiko
2024-09-12  3:06     ` Geliang Tang
2024-09-10  5:37 ` [PATCH mptcp-next v3 2/5] Squash to "mptcp: add sched_data helpers" Geliang Tang
2024-09-10  5:37 ` [PATCH mptcp-next v3 3/5] bpf: Register mptcp tracing kfunc set Geliang Tang
2024-09-10  5:37 ` [PATCH mptcp-next v3 4/5] selftests/bpf: Add mptcp_subflow bpf_iter test prog Geliang Tang
2024-09-10  5:37 ` [PATCH mptcp-next v3 5/5] selftests/bpf: Add mptcp_subflow bpf_iter subtest Geliang Tang
2024-09-10  6:02 ` [PATCH mptcp-next v3 0/5] add mptcp_subflow bpf_iter MPTCP CI
2024-09-10  6:30   ` Geliang Tang
2024-09-10  7:56     ` Matthieu Baerts
2024-09-10  8:42       ` Geliang Tang
2024-09-10  6:30 ` MPTCP CI [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=9c607dc6-979f-f6b4-3473-ec717f1df763@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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