From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selinux: Implement mptcp_add_subflow hook: Tests Results
Date: Wed, 14 Dec 2022 23:27:20 +0000 [thread overview]
Message-ID: <46af7f85-3769-ec6d-057a-acc75f8bcb9b@gmail.com> (raw)
In-Reply-To: <d6f04d238c8a797899d6cb543a43f75e544221af.1671054577.git.pabeni@redhat.com>
Hi Paolo,
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/6429528191926272
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6429528191926272/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Unstable: 1 failed test(s): packetdrill_mp_join 🔴:
- Task: https://cirrus-ci.com/task/6148053215215616
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6148053215215616/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5022153308372992
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5022153308372992/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5585103261794304
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5585103261794304/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/e34e1ddf3ddc
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:[~2022-12-14 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 22:01 [PATCH 0/2] lsm: introduce and use security_mptcp_add_subflow() Paolo Abeni
2022-12-14 22:01 ` [PATCH 1/2] security, lsm: Introduce security_mptcp_add_subflow() Paolo Abeni
2022-12-15 0:38 ` kernel test robot
2022-12-15 2:09 ` kernel test robot
2022-12-14 22:01 ` [PATCH 2/2] selinux: Implement mptcp_add_subflow hook Paolo Abeni
2022-12-14 22:15 ` selinux: Implement mptcp_add_subflow hook: Build Failure MPTCP CI
2022-12-14 23:27 ` MPTCP CI [this message]
2022-12-15 2:59 ` [PATCH 2/2] selinux: Implement mptcp_add_subflow hook kernel test robot
2022-12-14 22:13 ` [PATCH 0/2] lsm: introduce and use security_mptcp_add_subflow() Paolo Abeni
-- strict thread matches above, loose matches on Subject: below --
2022-12-19 17:33 [PATCH v2 2/2] selinux: Implement mptcp_add_subflow hook Paolo Abeni
2022-12-19 19:10 ` selinux: Implement mptcp_add_subflow hook: Tests Results MPTCP CI
2022-12-19 21:55 ` MPTCP CI
2023-01-17 7:36 [PATCH mptcp-next v2 13/13] selinux: Implement mptcp_add_subflow hook Paolo Abeni
2023-01-17 9:09 ` selinux: Implement mptcp_add_subflow hook: Tests Results MPTCP CI
2023-01-17 15:17 ` Paolo Abeni
2023-01-26 21:05 [PATCH v3 mptcp-next 15/15] selinux: Implement mptcp_add_subflow hook Paolo Abeni
2023-01-26 22:24 ` selinux: Implement mptcp_add_subflow hook: Tests Results MPTCP CI
2023-01-27 16:16 ` MPTCP CI
2023-01-27 16:27 ` Matthieu Baerts
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=46af7f85-3769-ec6d-057a-acc75f8bcb9b@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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