archive mirror
 help / color / mirror / Atom feed
From: MPTCP CI <>
To: Dmytro SHYTYI <>
Subject: Re: mptcp: Fast Open Mechanism: Tests Results
Date: Mon, 01 Aug 2022 02:59:54 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Dmytro,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: Script error! ❓:
  - :
  - Task:
  - Summary:

- KVM Validation: Script error! ❓:
  - :
  - Task:
  - Summary:

Initiator: Patchew Applier

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 \

For more details:

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 ;-)

MPTCP GH Action bot
Bot operated by Matthieu Baerts (Tessares)

  parent reply	other threads:[~2022-08-01  2:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  2:46 [RFC PATCH mptcp-next v4] mptcp: Fast Open Mechanism Dmytro SHYTYI
2022-08-01  2:57 ` mptcp: Fast Open Mechanism: Build Failure MPTCP CI
2022-08-01  2:59 ` MPTCP CI [this message]
2022-08-03  0:32 ` [RFC PATCH mptcp-next v4] mptcp: Fast Open Mechanism Mat Martineau
2022-08-03  7:36   ` Dmytro SHYTYI
  -- strict thread matches above, loose matches on Subject: below --
2022-05-22 18:39 [RFC PATCH mptcp-next v3] " Dmytro SHYTYI
2022-05-22 18:59 ` mptcp: Fast Open Mechanism: 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).