MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Thomas Haller <thaller@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: allow priviledged operations from user namespaces: Tests Results
Date: Fri, 05 Aug 2022 13:37:32 +0000	[thread overview]
Message-ID: <2c2acc73-a8e2-662e-8558-432efd4a49ad@gmail.com> (raw)
In-Reply-To: <20220805115020.525181-1-thaller@redhat.com>

Hi Thomas,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

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

- KVM Validation: debug:
  - Unstable: 2 failed test(s): kunit packetdrill_add_addr 🔴:
  - Task: https://cirrus-ci.com/task/5973058706997248
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5973058706997248/summary/summary.txt

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


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:[~2022-08-05 13:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 11:50 [PATCH] mptcp: allow priviledged operations from user namespaces Thomas Haller
2022-08-05 13:37 ` MPTCP CI [this message]
2022-08-09  0:04 ` Mat Martineau
2022-08-09 10:23   ` Thomas Haller
2022-08-09 10:25   ` Florian Westphal
2022-08-09 11:16     ` Florian Westphal
2022-08-10  7:42   ` [PATCH mptcp-next v2 1/2] " Thomas Haller
2022-08-10  7:42     ` [PATCH mptcp-next v2 2/2] mptcp: account memory allocation in mptcp_nl_cmd_add_addr() to user Thomas Haller
2022-08-10 23:14       ` Mat Martineau
2022-08-10 23:08     ` [PATCH mptcp-next v2 1/2] mptcp: allow priviledged operations from user namespaces Mat Martineau
2022-08-11 10:34       ` Matthieu Baerts
2022-08-24 20:37         ` Thomas Haller
2022-08-29 15:13           ` 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=2c2acc73-a8e2-662e-8558-432efd4a49ad@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=mptcp@lists.linux.dev \
    --cc=thaller@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