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: Thu, 07 Apr 2022 07:35:45 +0000 [thread overview]
Message-ID: <28d94849-2e24-c81d-243b-e1c5d7f5a97c@gmail.com> (raw)
In-Reply-To: <e639177ebf8e08c94df288a7b0f430718de81b5f.1649303876.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/6286185919152128
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6286185919152128/summary/summary.txt
- KVM Validation: debug:
- Unstable: 1 failed test(s): selftest_diag 🔴:
- Task: https://cirrus-ci.com/task/6423686008799232
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6423686008799232/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/0897208a28b5
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:[~2022-04-07 7:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 4:03 [PATCH mptcp-next v10 0/8] BPF packet scheduler Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 1/8] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 2/8] mptcp: register default scheduler Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 3/8] mptcp: add a new sysctl scheduler Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 4/8] mptcp: add sched in mptcp_sock Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 5/8] mptcp: add get_subflow wrapper Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 6/8] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 7/8] selftests: bpf: add bpf_first scheduler Geliang Tang
2022-04-07 4:03 ` [PATCH mptcp-next v10 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-07 7:35 ` MPTCP CI [this message]
2022-04-08 0:12 ` [PATCH mptcp-next v10 0/8] BPF packet scheduler Mat Martineau
-- 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-20 4:57 [PATCH mptcp-next v12 10/10] selftests: bpf: add bpf_first test Geliang Tang
2022-04-20 6:49 ` 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-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=28d94849-2e24-c81d-243b-e1c5d7f5a97c@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