mptcp.lists.linux.dev archive mirror
 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_red test: Tests Results
Date: Thu, 30 Jun 2022 10:32:37 +0000	[thread overview]
Message-ID: <076e8532-b07a-fb64-d5d1-2294226cfc49@gmail.com> (raw)
In-Reply-To: <22c84dbb74978d8062d453f6bc1857502078fc28.1656578856.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:
  - Unstable: 1 failed test(s): selftest_simult_flows - Critical: 2 Call Trace(s) ❌:
  - Task: https://cirrus-ci.com/task/5934869556494336
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5934869556494336/summary/summary.txt

- KVM Validation: debug:
  - Unstable: 1 failed test(s): selftest_mptcp_join - Critical: 2 Call Trace(s) ❌:
  - Task: https://cirrus-ci.com/task/5371919603073024
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5371919603073024/summary/summary.txt

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


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:[~2022-06-30 10:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  8:50 [PATCH mptcp-next v10 0/5] BPF redundant scheduler Geliang Tang
2022-06-30  8:50 ` [PATCH mptcp-next v10 1/5] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-06-30  8:50 ` [PATCH mptcp-next v10 2/5] mptcp: redundant subflows push pending Geliang Tang
2022-07-01 21:01   ` Mat Martineau
2022-06-30  8:50 ` [PATCH mptcp-next v10 3/5] mptcp: redundant subflows retrans support Geliang Tang
2022-06-30  8:50 ` [PATCH mptcp-next v10 4/5] selftests/bpf: Add bpf_red scheduler Geliang Tang
2022-06-30  8:50 ` [PATCH mptcp-next v10 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-30 10:32   ` MPTCP CI [this message]
2022-06-30 12:34     ` selftests/bpf: Add bpf_red test: Tests Results Geliang Tang
2022-07-01 19:16       ` Mat Martineau
2022-07-01 21:05         ` Mat Martineau
  -- strict thread matches above, loose matches on Subject: below --
2022-12-15 12:32 [PATCH mptcp-next v25 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-12-20  2:52 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-12-06 13:22 [PATCH mptcp-next v23 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-12-06 14:50 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-12-02 13:30 [PATCH mptcp-next v22 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-12-02 14:36 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-11-28  3:24 [PATCH mptcp-next v21 7/7] selftests/bpf: Add bpf_red test Geliang Tang
2022-11-28  5:02 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-11-08  9:08 [PATCH mptcp-next v18 15/15] selftests/bpf: Add bpf_red test Geliang Tang
2022-11-08 10:51 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-11-08  6:45 [PATCH mptcp-next v17 15/15] selftests/bpf: Add bpf_red test Geliang Tang
2022-11-08  8:28 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-10-21 11:00 [PATCH mptcp-next v15 19/19] selftests/bpf: Add bpf_red test Geliang Tang
2022-10-21 13:08 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-09-27 15:27 [PATCH mptcp-next v12 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-09-27 17:24 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-09-09  9:11 [PATCH mptcp-next v11 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-09-09 10:54 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-23 14:54 [PATCH mptcp-next v9 6/6] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-23 16:20 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-23 10:50 [PATCH mptcp-next v8 6/6] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-23 12:39 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-21  9:54 [PATCH mptcp-next v7 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-21 11:07 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-10 13:05 [PATCH mptcp-next v6 9/9] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-10 15:09 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-06 14:41 [PATCH mptcp-next v5 7/7] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-06 16:26 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-06  9:47 [PATCH mptcp-next v4 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-06 11:47 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-06-05 13:29 [PATCH mptcp-next v3 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-05 15:41 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-05-20  8:04 [PATCH mptcp-next 10/10] selftests/bpf: add bpf_red test Geliang Tang
2022-05-20  9:52 ` selftests/bpf: add bpf_red 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=076e8532-b07a-fb64-d5d1-2294226cfc49@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 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).