MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Breno Leitao <leitao@debian.org>
Cc: mptcp@lists.linux.dev
Subject: Re: net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results
Date: Tue, 06 Jun 2023 19:09:31 +0000	[thread overview]
Message-ID: <14ccfd46-2000-992d-a196-608dc5f9dcdb@gmail.com> (raw)
In-Reply-To: <20230606180045.827659-1-leitao@debian.org>

Hi Breno,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal (except selftest_mptcp_join):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/5521599395266560
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5521599395266560/summary/summary.txt

- KVM Validation: debug (only selftest_mptcp_join):
  - Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
  - Task: https://cirrus-ci.com/task/5732705627799552
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5732705627799552/summary/summary.txt

- KVM Validation: debug (except selftest_mptcp_join):
  - Unstable: 1 failed test(s): packetdrill_add_addr 🔴:
  - Task: https://cirrus-ci.com/task/4606805720956928
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4606805720956928/summary/summary.txt

- KVM Validation: normal (only selftest_mptcp_join):
  - Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
  - Task: https://cirrus-ci.com/task/6647499302109184
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6647499302109184/summary/summary.txt

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/8116764b617d


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-debug

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 (Tessares)

  reply	other threads:[~2023-06-06 19:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 18:00 [PATCH net-next v6] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-06-06 19:09 ` MPTCP CI [this message]
2023-06-07 12:15 ` Willem de Bruijn
2023-06-07 13:25 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-07 14:45 ` [PATCH net-next v6] net: ioctl: Use kernel memory on protocol ioctl callbacks David Ahern
2023-06-08  7:39   ` Ido Schimmel
2023-06-07 15:57 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-07 17:31 ` [PATCH net-next v6] net: ioctl: Use kernel memory on protocol ioctl callbacks Kuniyuki Iwashima
2023-06-08  8:43   ` Breno Leitao
2023-06-08 13:57     ` Paolo Abeni
2023-06-08 14:35       ` Breno Leitao
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 15:27 [PATCH net-next v7] " Breno Leitao
2023-06-09 17:37 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-09 21:01 ` MPTCP CI
2023-06-02 16:30 [PATCH net-next v5] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-06-02 18:03 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-30 17:53 [PATCH net-next v4] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-30 19:38 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-25 12:54 [PATCH net-next v3] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-25 15:16 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-22 13:47 [PATCH v2] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-22 17:11 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-19 13:58 [PATCH 1/1] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-19 15:25 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-19 18:03   ` Mat Martineau
2023-05-22 11:17     ` Breno Leitao

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=14ccfd46-2000-992d-a196-608dc5f9dcdb@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=leitao@debian.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