All of lore.kernel.org
 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: refactor sndbuf auto-tuning.: Tests Results
Date: Fri, 22 Sep 2023 17:35:36 +0000	[thread overview]
Message-ID: <8acb8ed1-4173-9e70-dc5f-e21d405dc671@gmail.com> (raw)
In-Reply-To: <6e31fe305493173f6c2e33f6351da074d9068a77.1695368456.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):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/4847632003104768
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4847632003104768/summary/summary.txt

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

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

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

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


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:[~2023-09-22 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  7:42 [PATCH v5 mptcp-next 0/4] mptcp: misc improvement Paolo Abeni
2023-09-22  7:42 ` [PATCH v5 mptcp-next 1/4] mptcp: fix delegated action races Paolo Abeni
2023-09-22  7:43 ` [PATCH v5 mptcp-next 2/4] mptcp: consolidate sockopt synchronization Paolo Abeni
2023-09-22  7:43 ` [PATCH v5 mptcp-next 3/4] mptcp: ignore notsent_lowat setting at the subflow level Paolo Abeni
2023-09-22  7:43 ` [PATCH v5 mptcp-next 4/4] mptcp: refactor sndbuf auto-tuning Paolo Abeni
2023-09-22  9:33   ` mptcp: refactor sndbuf auto-tuning.: Tests Results MPTCP CI
2023-09-22 17:35   ` MPTCP CI [this message]
2023-09-22 16:17 ` [PATCH v5 mptcp-next 0/4] mptcp: misc improvement Mat Martineau
2023-09-23  8:32 ` Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2023-09-20  9:09 [PATCH mptcp-next v4 4/4] mptcp: refactor sndbuf auto-tuning Paolo Abeni
2023-09-20 10:14 ` mptcp: refactor sndbuf auto-tuning.: Tests Results MPTCP CI
2023-09-15 14:19 [PATCH v3 mptcp-next 3/3] mptcp: refactor sndbuf auto-tuning Paolo Abeni
2023-09-15 16:25 ` mptcp: refactor sndbuf auto-tuning.: Tests Results MPTCP CI
2023-09-14 17:02 [PATCH mptcp-next v2 3/3] mptcp: refactor sndbuf auto-tuning Paolo Abeni
2023-09-14 18:24 ` mptcp: refactor sndbuf auto-tuning.: Tests Results MPTCP CI
2023-09-13 21:05 [PATCH mptcp-next 3/3] mptcp: refactor sndbuf auto-tuning Paolo Abeni
2023-09-13 22:17 ` mptcp: refactor sndbuf auto-tuning.: 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=8acb8ed1-4173-9e70-dc5f-e21d405dc671@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.