All of lore.kernel.org
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Jason Xing <kernelxing@tencent.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH net-next v8 0/7] Implement reset reason mechanism to detect
Date: Tue, 23 Apr 2024 08:15:52 +0000	[thread overview]
Message-ID: <7aaa0898-bd92-1edd-193f-7b479ca219f3@gmail.com> (raw)
In-Reply-To: <20240423072137.65168-1-kerneljasonxing@gmail.com>

Hi Jason,

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: Unstable: 1 failed test(s): selftest_mptcp_join 🔴
- KVM Validation: btf (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/8796605426

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


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-04-23  8:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  7:21 [PATCH net-next v8 0/7] Implement reset reason mechanism to detect Jason Xing
2024-04-23  7:21 ` [PATCH net-next v8 1/7] net: introduce rstreason to detect why the RST is sent Jason Xing
2024-04-23  9:59   ` Matthieu Baerts
2024-04-23  7:21 ` [PATCH net-next v8 2/7] rstreason: prepare for passive reset Jason Xing
2024-04-23 10:00   ` Matthieu Baerts
2024-04-23  7:21 ` [PATCH net-next v8 3/7] rstreason: prepare for active reset Jason Xing
2024-04-23 10:00   ` Matthieu Baerts
2024-04-23  7:21 ` [PATCH net-next v8 4/7] tcp: support rstreason for passive reset Jason Xing
2024-04-23  7:21 ` [PATCH net-next v8 5/7] mptcp: " Jason Xing
2024-04-23 10:02   ` Matthieu Baerts
2024-04-23 10:57     ` Jason Xing
2024-04-23  7:21 ` [PATCH net-next v8 6/7] mptcp: introducing a helper into active reset logic Jason Xing
2024-04-23 10:02   ` Matthieu Baerts
2024-04-23  7:21 ` [PATCH net-next v8 7/7] rstreason: make it work in trace world Jason Xing
2024-04-23  8:15 ` 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=7aaa0898-bd92-1edd-193f-7b479ca219f3@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=kernelxing@tencent.com \
    --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.