MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Dmytro Shytyi <dmytro@shytyi.net>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: reuse tcp_sendmsg_fastopen(): Tests Results
Date: Fri, 23 Sep 2022 01:49:48 +0000	[thread overview]
Message-ID: <7ec77f05-2684-741f-001a-cc8164a8dba8@gmail.com> (raw)
In-Reply-To: <20220923001530.9722-4-dmytro@shytyi.net>

Hi Dmytro,

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/4837384788377600
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4837384788377600/summary/summary.txt

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

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


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-23  1:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  0:15 [RFC PATCH mptcp-next v10 0/3] mptcp: Fast Open Mechanism: Dmytro Shytyi
2022-09-23  0:15 ` [RFC PATCH mptcp-next v10 1/3] mptcp: add mptcp_setsockopt_fastopen Dmytro Shytyi
2022-09-23  0:15 ` [RFC PATCH mptcp-next v10 2/3] mptcp: add mptcp_stream_connect to *.h Dmytro Shytyi
2022-09-23  0:15 ` [RFC PATCH mptcp-next v10 3/3] mptcp: reuse tcp_sendmsg_fastopen() Dmytro Shytyi
2022-09-23  0:44   ` mptcp: reuse tcp_sendmsg_fastopen(): Build Failure MPTCP CI
2022-09-23  1:49   ` MPTCP CI [this message]
2022-09-23  2:26 ` [RFC PATCH mptcp-next v10 0/3] mptcp: Fast Open Mechanism: Dmytro Shytyi

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=7ec77f05-2684-741f-001a-cc8164a8dba8@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=dmytro@shytyi.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