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_stale test: Tests Results
Date: Tue, 06 Jun 2023 10:26:29 +0000 [thread overview]
Message-ID: <f0363211-960d-5074-eabd-52a3b1667010@gmail.com> (raw)
In-Reply-To: <1cf433961986135e884dfc35b981c82ec6a5f528.1686041504.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 (except selftest_mptcp_join):
- Unstable: 2 failed test(s): packetdrill_fastopen packetdrill_sockopts 🔴:
- Task: https://cirrus-ci.com/task/4723489714733056
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4723489714733056/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6412339574996992
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6412339574996992/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5849389621575680
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5849389621575680/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Unstable: 2 failed test(s): packetdrill_fastopen selftest_diag 🔴:
- Task: https://cirrus-ci.com/task/5286439668154368
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5286439668154368/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/a49d687bcd1f
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)
next prev parent reply other threads:[~2023-06-06 10:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:59 [PATCH mptcp-next v6 00/18] BPF packet scheduler updates Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 01/18] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 02/18] Squash to "mptcp: add sched in mptcp_sock" Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 03/18] Squash to "mptcp: add scheduler wrappers" Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 04/18] mptcp: add last_snd in sched_data Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 05/18] mptcp: add snd_burst " Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 06/18] mptcp: register default scheduler Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 07/18] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 08/18] Squash to "selftests/bpf: Add mptcp sched structs" Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 09/18] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 10/18] mptcp: rename __mptcp_set_timeout Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 11/18] mptcp: add two wrappers needed by bpf_burst Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 12/18] bpf: Add bpf_burst write accesses Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 13/18] bpf: Export more bpf_burst related functions Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 14/18] selftests/bpf: Add bpf_burst scheduler Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 15/18] selftests/bpf: Add bpf_burst test Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 16/18] bpf: Add subflow flags write access Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 17/18] selftests/bpf: Add bpf_stale scheduler Geliang Tang
2023-06-06 8:59 ` [PATCH mptcp-next v6 18/18] selftests/bpf: Add bpf_stale test Geliang Tang
2023-06-06 9:35 ` selftests/bpf: Add bpf_stale test: Build Failure MPTCP CI
2023-06-06 10:26 ` MPTCP CI [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-10 14:10 [RFC mptcp-next 11/11] selftests/bpf: Add bpf_stale test Geliang Tang
2023-08-10 15:23 ` selftests/bpf: Add bpf_stale test: Tests Results MPTCP CI
2023-08-03 6:51 [PATCH mptcp-next v2 2/2] selftests/bpf: Add bpf_stale test Geliang Tang
2023-08-03 8:02 ` selftests/bpf: Add bpf_stale test: Tests Results MPTCP CI
2023-08-02 5:10 [PATCH mptcp-next 3/3] selftests/bpf: Add bpf_stale test Geliang Tang
2023-08-02 6:19 ` selftests/bpf: Add bpf_stale test: Tests Results MPTCP CI
2023-06-14 2:21 [PATCH mptcp-next v9 23/23] selftests/bpf: Add bpf_stale test Geliang Tang
2023-06-14 4:41 ` selftests/bpf: Add bpf_stale test: Tests Results MPTCP CI
2023-06-14 6:22 ` MPTCP CI
2023-06-08 5:46 [PATCH mptcp-next v8 17/17] selftests/bpf: Add bpf_stale test Geliang Tang
2023-06-08 6:56 ` selftests/bpf: Add bpf_stale test: Tests Results MPTCP CI
2023-06-13 10:57 ` MPTCP CI
2023-06-07 8:38 [PATCH mptcp-next v7 19/19] selftests/bpf: Add bpf_stale test Geliang Tang
2023-06-07 9:42 ` selftests/bpf: Add bpf_stale test: Tests Results MPTCP CI
2023-06-06 6:45 [PATCH mptcp-next v5 18/18] selftests/bpf: Add bpf_stale test Geliang Tang
2023-06-06 8:20 ` selftests/bpf: Add bpf_stale 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=f0363211-960d-5074-eabd-52a3b1667010@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.