MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: flush userspace addrs list: Tests Results
Date: Wed, 21 Feb 2024 15:47:32 +0000	[thread overview]
Message-ID: <ac90ab4a-b6f0-30c8-6380-49c8e8476fd2@gmail.com> (raw)
In-Reply-To: <bb5e3f97c4a225f616d82112570514114fce00c5.1708497039.git.tanggeliang@kylinos.cn>

Hi Geliang,

Thank you for your modifications, that's great!

Our CI (GitHub Action) did some validations and here is its report:

- KVM Validation: normal:
  - Unstable: 1 failed test(s): packetdrill_regressions 🔴:
  - Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/7991240119

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


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-normal

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 (NGI0 Core)

  reply	other threads:[~2024-02-21 15:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  6:31 [PATCH mptcp-next 0/8] some cleanups Geliang Tang
2024-02-21  6:31 ` [PATCH mptcp-next 1/8] mptcp: make pm_remove_addrs_and_subflows static Geliang Tang
2024-02-21  6:31 ` [PATCH mptcp-next 2/8] mptcp: drop duplicate header inclusions Geliang Tang
2024-02-21  6:31 ` [PATCH mptcp-next 3/8] mptcp: update set_flags interfaces Geliang Tang
2024-02-21  6:31 ` [PATCH mptcp-next 4/8] mptcp: set error messages for set_flags Geliang Tang
2024-02-21 16:18   ` Matthieu Baerts
2024-02-21  6:31 ` [PATCH mptcp-next 5/8] mptcp: drop lookup_by_id in lookup_addr Geliang Tang
2024-02-21  6:31 ` [PATCH mptcp-next 6/8] mptcp: add use_id parameter for addresses_equal Geliang Tang
2024-02-21 16:19   ` Matthieu Baerts
2024-02-21  6:31 ` [PATCH mptcp-next 7/8] mptcp: add check_id for lookup_anno_list_by_saddr Geliang Tang
2024-02-21 16:20   ` Matthieu Baerts
2024-02-21  6:31 ` [PATCH mptcp-next 8/8] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-02-21 15:47   ` MPTCP CI [this message]
2024-02-21 16:21   ` Matthieu Baerts
2024-02-21 16:18 ` [PATCH mptcp-next 0/8] some cleanups Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2024-02-22  8:03 [PATCH mptcp-next v2 7/7] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-02-22  8:51 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-01-18  6:12 [PATCH mptcp-next v10 23/23] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-01-18  7:24 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-01-18  8:03 ` MPTCP CI
2024-01-16  3:35 [PATCH mptcp-next v9 23/23] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-01-16  4:45 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-01-16  5:00 ` MPTCP CI
2024-01-10 13:19 [PATCH mptcp-next v8 23/23] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-01-10 14:23 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-01-10 14:59 ` MPTCP CI
2023-12-30  2:48 [PATCH mptcp-next v7 24/24] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-01-02 11:58 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-01-02 11:59   ` Matthieu Baerts
2024-01-02 14:14 ` MPTCP CI
2024-01-06  2:55 ` 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=ac90ab4a-b6f0-30c8-6380-49c8e8476fd2@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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