mptcp.lists.linux.dev archive mirror
 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: use common helper for rmem memory accounting: Tests Results
Date: Fri, 29 Jul 2022 16:06:53 +0000	[thread overview]
Message-ID: <06b4dceb-92c9-0b4e-426e-173a1e2dc85e@gmail.com> (raw)
In-Reply-To: <f253e24227ce660aae19714c2cca1726ee087184.1659107989.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: Script error! ❓:
  - :
  - Task: https://cirrus-ci.com/task/5166180951392256
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5166180951392256/summary/summary.txt

- KVM Validation: Script error! ❓:
  - :
  - Task: https://cirrus-ci.com/task/6292080858234880
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6292080858234880/summary/summary.txt

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


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)

  parent reply	other threads:[~2022-07-29 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 15:33 [PATCH mptcp-next 0/4] mptcp: just another receive path refactor Paolo Abeni
2022-07-29 15:33 ` [PATCH mptcp-next 1/4] mptcp: move RCVPRUNE event later Paolo Abeni
2022-07-29 15:33 ` [PATCH mptcp-next 2/4] mptcp: more accurate receive buffer updates Paolo Abeni
2022-07-29 18:24   ` kernel test robot
2022-07-29 19:05   ` kernel test robot
2022-07-29 15:33 ` [PATCH mptcp-next 3/4] mptcp: move msk input path under full msk socket lock Paolo Abeni
2022-07-29 17:43   ` kernel test robot
2022-07-29 19:45   ` kernel test robot
2022-07-29 15:33 ` [PATCH mptcp-next 4/4] mptcp: use common helper for rmem memory accounting Paolo Abeni
2022-07-29 15:47   ` mptcp: use common helper for rmem memory accounting: Build Failure MPTCP CI
2022-07-29 16:09     ` Paolo Abeni
2022-07-29 16:06   ` MPTCP CI [this message]
2022-07-29 18:14 [PATCH v2 mptcp-next 4/4] mptcp: use common helper for rmem memory accounting Paolo Abeni
2022-07-29 21:20 ` mptcp: use common helper for rmem memory accounting: Tests Results MPTCP CI
2022-07-30  8:04 [PATCH v3 mptcp-next 4/4] mptcp: use common helper for rmem memory accounting Paolo Abeni
2022-07-30  9:59 ` mptcp: use common helper for rmem memory accounting: 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=06b4dceb-92c9-0b4e-426e-173a1e2dc85e@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;
as well as URLs for NNTP newsgroup(s).