All of lore.kernel.org
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: bpf: add bpf_first test: Tests Results
Date: Wed, 20 Apr 2022 06:49:37 +0000	[thread overview]
Message-ID: <6c37f1c6-0cb1-b284-375b-9e7f0ef7cb3c@gmail.com> (raw)
In-Reply-To: <7072b5ca4b8e6d710506a789c4e962c9e33cc54d.1650430389.git.geliang.tang@suse.com>

Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

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

- KVM Validation: debug:
  - Unstable: 1 failed test(s): selftest_diag - Critical: KMemLeak ❌:
  - Task: https://cirrus-ci.com/task/4914771186155520
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4914771186155520/summary/summary.txt

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


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-04-20  6:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  4:56 [PATCH mptcp-next v12 00/10] BPF packet scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 01/10] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-04-20 16:22   ` Matthieu Baerts
2022-04-20  4:57 ` [PATCH mptcp-next v12 02/10] mptcp: register default scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 03/10] mptcp: add a new sysctl scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 04/10] mptcp: add sched in mptcp_sock Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 05/10] mptcp: add get_subflow wrapper Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 06/10] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 07/10] mptcp: add last_snd write access Geliang Tang
2022-04-20 16:23   ` Matthieu Baerts
2022-04-20 16:44   ` Matthieu Baerts
2022-04-21  6:42   ` kernel test robot
2022-04-20  4:57 ` [PATCH mptcp-next v12 08/10] mptcp: add call_me_again flag Geliang Tang
2022-04-20 16:40   ` Matthieu Baerts
2022-04-20  4:57 ` [PATCH mptcp-next v12 09/10] selftests: bpf: add bpf_first scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 10/10] selftests: bpf: add bpf_first test Geliang Tang
2022-04-20  5:14   ` selftests: bpf: add bpf_first test: Build Failure MPTCP CI
2022-04-20  6:49   ` MPTCP CI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-01 13:48 [PATCH mptcp-next v18 7/7] selftests: bpf: add bpf_first test Geliang Tang
2022-05-01 15:37 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-28  5:23 [PATCH mptcp-next v17 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-28  6:52 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-27  1:56 [PATCH mptcp-next v16 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-27  3:30 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-22  7:42 [PATCH mptcp-next v14 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-22  9:44 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-21  6:22 [PATCH mptcp-next v13 9/9] selftests: bpf: add bpf_first test Geliang Tang
2022-04-21  7:56 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-08 15:38 [PATCH mptcp-next v11 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-08 18:44 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-07  4:03 [PATCH mptcp-next v10 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-07  7:35 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-04  2:10 [PATCH mptcp-next v9 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-05 10:23 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-03-29  7:09 [PATCH mptcp-next v8 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-03-30 18:04 ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-03-25 16:12 [PATCH mptcp-next v6 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-03-30 20:51 ` selftests: bpf: add bpf_first test: 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=6c37f1c6-0cb1-b284-375b-9e7f0ef7cb3c@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=geliang.tang@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.