MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Stefan Metzmacher <metze@samba.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [RFC PATCH 0/4] net/io_uring: pass a kernel pointer via optlen_t to proto[_ops].getsockopt()
Date: Mon, 31 Mar 2025 21:53:43 +0000	[thread overview]
Message-ID: <263a9fb7-d230-d10d-9830-b79b5d8ea5b7@gmail.com> (raw)
In-Reply-To: <cover.1743449872.git.metze@samba.org>

Hi Stefan,

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: Critical: Global Timeout ❌
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Unstable: 1 failed test(s): bpftest_test_progs_mptcp 🔴
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/14180807770

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


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:[~2025-03-31 21:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 20:10 [RFC PATCH 0/4] net/io_uring: pass a kernel pointer via optlen_t to proto[_ops].getsockopt() Stefan Metzmacher
2025-03-31 20:10 ` [RFC PATCH 1/4] net: introduce get_optlen() and put_optlen() helpers Stefan Metzmacher
2025-04-01 12:17   ` Breno Leitao
2025-04-01 12:22     ` Stefan Metzmacher
2025-03-31 20:10 ` [RFC PATCH 2/4] net: pass 'optlen_t' to proto[ops].getsockopt() hooks Stefan Metzmacher
2025-03-31 20:27   ` Stefan Metzmacher
2025-03-31 20:10 ` [RFC PATCH 3/4] net: pass a kernel pointer via " Stefan Metzmacher
2025-03-31 21:49   ` David Laight
2025-04-01  8:24     ` Stefan Metzmacher
2025-03-31 20:10 ` [RFC PATCH 4/4] io_uring: let io_uring_cmd_getsockopt() allow level other than SOL_SOCKET Stefan Metzmacher
2025-03-31 21:04 ` [RFC PATCH 0/4] net/io_uring: pass a kernel pointer via optlen_t to proto[_ops].getsockopt() Stanislav Fomichev
2025-04-01  8:19   ` Stefan Metzmacher
2025-04-01 13:37     ` Stefan Metzmacher
2025-04-01 13:48       ` Stefan Metzmacher
2025-04-01 15:35         ` Breno Leitao
2025-04-01 15:45           ` Stanislav Fomichev
2025-04-01 21:20             ` Stefan Metzmacher
2025-04-01 22:04               ` Stanislav Fomichev
2025-04-01 22:53                 ` Stefan Metzmacher
2025-04-02 12:29                   ` David Laight
2025-04-02 14:19                     ` Stanislav Fomichev
2025-04-02 20:46                       ` David Laight
2025-04-02 21:07                         ` Linus Torvalds
2025-04-02 21:21                         ` Stanislav Fomichev
2025-04-02 22:38                           ` David Laight
2025-04-02 23:39                             ` Stanislav Fomichev
2025-03-31 21:53 ` MPTCP CI [this message]
2025-04-01  6:37 ` MPTCP CI
2025-04-02  0:40 ` Linus Torvalds
2025-04-02 12:35   ` David Laight

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=263a9fb7-d230-d10d-9830-b79b5d8ea5b7@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=metze@samba.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