MPTCP Linux Development
 help / color / mirror / Atom feed
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: Thu, 26 Jan 2023 22:24:20 +0000	[thread overview]
Message-ID: <9462c399-1aa3-083e-c253-2adce228a105@gmail.com> (raw)
In-Reply-To: <4d5c94f133002e76ecb74c3303ab350df9175e90.1674767058.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):
  - Unstable: 1 failed test(s): packetdrill_syscalls 🔴:
  - Task: https://cirrus-ci.com/task/5066988909756416
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5066988909756416/summary/summary.txt

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

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

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

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


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-01-26 22:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 21:05 [PATCH v3 mptcp-next 00/15] mptcp: refactor first subflow init Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 01/15] mptcp: use mptcp_schedule_work() instead of open-codying it Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 02/15] mptcp: fix locking for setsockopt corner-case Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 03/15] mptcp: fix locking for in-kernel listener creation Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 04/15] mptcp: refactor passive socket initialization Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 05/15] mptcp: drop unneeded argument Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 06/15] mptcp: drop legacy code Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 07/15] mptcp: avoid unneeded __mptcp_nmpc_socket() usage Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 08/15] mptcp: move fastopen subflow check inside mptcp_sendmsg_fastopen() Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 09/15] mptcp: move first subflow allocation at mpc access time Paolo Abeni
2023-01-27 14:04   ` Matthieu Baerts
2023-01-26 21:05 ` [PATCH v3 mptcp-next 10/15] mptcp: do not keep around the first subflow after disconnect Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 11/15] mptcp: fastclose msk when cleaning unaccepted sockets Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 12/15] inet: factor out locked section of inet_accept() in a new helper Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 13/15] mptcp: refactor mptcp_stream_accept() Paolo Abeni
2023-01-26 21:05 ` [PATCH v3 mptcp-next 14/15] security, lsm: Introduce security_mptcp_add_subflow() 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   ` MPTCP CI [this message]
2023-01-27 16:16   ` selinux: Implement mptcp_add_subflow hook: Tests Results MPTCP CI
2023-01-27 16:27     ` Matthieu Baerts
2023-01-27 14:04 ` [PATCH v3 mptcp-next 00/15] mptcp: refactor first subflow init Matthieu Baerts
2023-01-30 11:27   ` Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
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
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
2022-12-14 22:01 [PATCH 2/2] selinux: Implement mptcp_add_subflow hook Paolo Abeni
2022-12-14 23:27 ` selinux: Implement mptcp_add_subflow hook: Tests Results MPTCP CI

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=9462c399-1aa3-083e-c253-2adce228a105@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