mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Benjamin Hesmans <benjamin.hesmans@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: poll allow write call before actual connect: Tests Results
Date: Thu, 22 Sep 2022 16:05:52 +0000	[thread overview]
Message-ID: <a781e577-8e34-d64d-2bcb-1c9443fde8e4@gmail.com> (raw)
In-Reply-To: <20220922135627.2019807-5-benjamin.hesmans@tessares.net>

Hi Benjamin,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

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

- KVM Validation: debug:
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/6450968651890688
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6450968651890688/summary/summary.txt

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


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-09-22 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 13:56 [PATCH mptcp-next v2 0/4] mptcp: add support for TFO, sender side only Benjamin Hesmans
2022-09-22 13:56 ` [PATCH mptcp-next v2 1/4] mptcp: add TCP_FASTOPEN_CONNECT socket option Benjamin Hesmans
2022-09-22 13:56 ` [PATCH mptcp-next v2 2/4] tcp: export tcp_sendmsg_fastopen Benjamin Hesmans
2022-09-22 13:56 ` [PATCH mptcp-next v2 3/4] mptcp: handle defer connect in mptcp_sendmsg Benjamin Hesmans
2022-09-22 13:56 ` [PATCH mptcp-next v2 4/4] mptcp: poll allow write call before actual connect Benjamin Hesmans
2022-09-22 14:42   ` mptcp: poll allow write call before actual connect: Tests Results MPTCP CI
2022-09-22 16:05   ` MPTCP CI [this message]
2022-09-22 14:36 ` [PATCH mptcp-next v2 0/4] mptcp: add support for TFO, sender side only Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2022-09-23 12:19 [PATCH mptcp-next v3 4/4] mptcp: poll allow write call before actual connect Benjamin Hesmans
2022-09-23 15:21 ` mptcp: poll allow write call before actual connect: Tests Results MPTCP CI
2022-09-21 15:25 [PATCH mptcp-next v1 5/5] mptcp: poll allow write call before actual connect Benjamin Hesmans
2022-09-21 16:52 ` mptcp: poll allow write call before actual connect: 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=a781e577-8e34-d64d-2bcb-1c9443fde8e4@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=benjamin.hesmans@tessares.net \
    --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;
as well as URLs for NNTP newsgroup(s).