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: mptcp: corner case locking for rx path fields initialization: Tests Results
Date: Wed, 17 Jan 2024 02:57:38 +0000	[thread overview]
Message-ID: <2e142d85-8e41-3f91-8426-0e00de9daf50@gmail.com> (raw)
In-Reply-To: <56241fbd64982b15aed04269c8b963206661acea.1705331716.git.pabeni@redhat.com>

Hi Paolo,

Thank you for your modifications, that's great!

Our CI (GitHub Action) did some validations and here is its report:

- KVM Validation: normal:
  - Critical: 1 Call Trace(s) - Critical: Unexpected stop of the VM ❌:
  - Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/7550415246

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


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-normal

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-01-17  2:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 15:16 [PATCH mptcp-net 0/4] mptcp: locking cleanup Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 1/4] mptcp: drop the push_pending field Paolo Abeni
2024-02-08 11:36   ` Matthieu Baerts
2024-02-08 15:12     ` Paolo Abeni
2024-02-08 18:05       ` Matthieu Baerts
2024-02-08 18:07         ` Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 2/4] mptcp: fix rcv space initialization Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 3/4] mptcp: fix more tx path fields initialization Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 4/4] mptcp: corner case locking for rx " Paolo Abeni
2024-01-15 16:13   ` mptcp: corner case locking for rx path fields initialization: Tests Results MPTCP CI
2024-01-15 17:07   ` MPTCP CI
2024-01-17  2:57   ` MPTCP CI [this message]
2024-01-17  3:54   ` MPTCP CI
2024-01-17  7:01   ` MPTCP CI
2024-01-17  2:32 ` [PATCH mptcp-net 0/4] mptcp: locking cleanup Mat Martineau
2024-01-17 10:30   ` Paolo Abeni
2024-01-17 11:58 ` 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=2e142d85-8e41-3f91-8426-0e00de9daf50@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