MPTCP Linux Development
 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: implement connection level timeout.: Tests Results
Date: Tue, 29 Aug 2023 16:43:51 +0000	[thread overview]
Message-ID: <df187c8f-c21f-b403-9712-e9df3d0be783@gmail.com> (raw)
In-Reply-To: <07268fba668d7645da445279581ecef9178c1b01.1693322440.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):
  - Unstable: 1 failed test(s): selftest_simult_flows 🔴:
  - Task: https://cirrus-ci.com/task/6536319392808960
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6536319392808960/summary/summary.txt

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

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

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

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


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)

  reply	other threads:[~2023-08-29 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 15:39 [PATCH mptcp-next v2 0/2] mptcp: fix another close hang-up Paolo Abeni
2023-08-29 15:39 ` [PATCH mptcp-next v2 1/2] mptcp: rename timer related helper to less confusing names Paolo Abeni
2023-08-29 15:39 ` [PATCH mptcp-next v2 2/2] mptcp: implement connection level timeout Paolo Abeni
2023-08-29 16:43   ` MPTCP CI [this message]
2023-08-30 15:30 ` [PATCH mptcp-next v2 0/2] mptcp: fix another close hang-up Paolo Abeni
  -- strict thread matches above, loose matches on Subject: below --
2023-09-01 11:11 [PATCH mptcp-next v4 2/2] mptcp: implement connection level timeout Paolo Abeni
2023-09-01 12:22 ` mptcp: implement connection level timeout.: Tests Results MPTCP CI
2023-09-01  9:27 [PATCH MPTCP-next v3 2/2] mptcp: implement connection level timeout Paolo Abeni
2023-09-01 11:27 ` mptcp: implement connection level timeout.: Tests Results MPTCP CI
2023-08-28 11:03 [PATCH mptcp-next 2/2] mptcp: implement connection level timeout Paolo Abeni
2023-08-28 12:07 ` mptcp: implement connection level timeout.: 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=df187c8f-c21f-b403-9712-e9df3d0be783@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