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, 30 May 2023 19:38:27 +0000 [thread overview]
Message-ID: <ddfea6e2-4636-1dce-946a-9ee45b93644d@gmail.com> (raw)
In-Reply-To: <20230530175403.2434218-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/4661059747840000
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4661059747840000/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Unstable: 5 failed test(s): packetdrill_add_addr packetdrill_fastopen packetdrill_mp_capable packetdrill_mp_reset selftest_diag 🔴:
- Task: https://cirrus-ci.com/task/5325149604413440
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5325149604413440/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6349909608103936
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6349909608103936/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5314839199875072
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5314839199875072/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/594d5a8a3320
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)
next prev parent reply other threads:[~2023-05-30 19:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 17:53 [PATCH net-next v4] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-30 17:53 ` Breno Leitao
2023-05-30 19:38 ` MPTCP CI [this message]
2023-05-31 7:01 ` Willem de Bruijn
2023-05-31 7:01 ` Willem de Bruijn
2023-06-02 16:19 ` Breno Leitao
2023-06-02 16:19 ` Breno Leitao
2023-05-31 13:36 ` kernel test robot
2023-05-31 13:36 ` kernel test robot
2023-06-01 3:27 ` kernel test robot
2023-06-01 3:27 ` kernel test robot
-- 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-06 18:00 [PATCH net-next v6] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-06-06 19:09 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-07 13:25 ` MPTCP CI
2023-06-07 15:57 ` 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-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=ddfea6e2-4636-1dce-946a-9ee45b93644d@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 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.