MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: configs/debug: add NET debug config: Tests Results
Date: Mon, 12 Feb 2024 12:36:20 +0000	[thread overview]
Message-ID: <06115d45-5572-bdf2-726c-628d64863862@gmail.com> (raw)
In-Reply-To: <20240212-kconfig-debug-enable-net-v1-1-fb026de8174c@kernel.org>

Hi Matthieu,

Thank you for your modifications, that's great!

Our CI (Cirrus) did some validations with a debug kernel and here is its report:

- KVM Validation: debug (except selftest_mptcp_join):
  - Script error! ❓:
  - Task: https://cirrus-ci.com/task/5661347283730432
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5661347283730432/summary/summary.txt

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

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


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 (NGI0 Core)

  parent reply	other threads:[~2024-02-12 12:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 10:47 [PATCH] configs/debug: add NET debug config Matthieu Baerts (NGI0)
2024-02-12 11:42 ` configs/debug: add NET debug config: Tests Results MPTCP CI
2024-02-12 12:36 ` MPTCP CI [this message]
2024-02-12 13:42 ` MPTCP CI
2024-02-12 18:39 ` [PATCH] configs/debug: add NET debug config Kees Cook
2024-02-13  1:02   ` Jakub Kicinski
2024-02-13  1:27     ` Andrew Morton
2024-02-13  1:52     ` Kees Cook
2024-02-12 19:32 ` configs/debug: add NET debug config: Tests Results MPTCP CI
2024-02-12 19:52 ` MPTCP CI
2024-02-16  1:50 ` [PATCH] configs/debug: add NET debug config patchwork-bot+netdevbpf

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=06115d45-5572-bdf2-726c-628d64863862@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=matttbe@kernel.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