From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results
Date: Sat, 27 May 2023 15:28:54 +0000 [thread overview]
Message-ID: <3ea4474b-df97-b641-4f4e-fb24b84570cf@gmail.com> (raw)
In-Reply-To: <ef47cf1485fc292a8f613c3f507dab8c6e7c7a65.1685191581.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: 1 failed test(s): selftest_simult_flows 🔴:
- Task: https://cirrus-ci.com/task/6601570566012928
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6601570566012928/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6707669310898176
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6707669310898176/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Unstable: 3 failed test(s): packetdrill_add_addr packetdrill_fastopen selftest_diag - Critical: 1 Call Trace(s) ❌:
- Task: https://cirrus-ci.com/task/5897883124236288
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5897883124236288/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Critical: 1 Call Trace(s) ❌:
- Task: https://cirrus-ci.com/task/5003560975335424
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5003560975335424/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/f83d4fc5e61e
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-05-27 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 12:55 [PATCH mptcp-next 0/8] save sched_data at mptcp_sock Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 1/8] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 2/8] Squash to "mptcp: add sched in mptcp_sock" Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 3/8] Squash to "mptcp: add scheduler wrappers" Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 4/8] mptcp: add last_snd in sched_data Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 5/8] mptcp: add snd_burst " Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 6/8] mptcp: register default scheduler Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 7/8] Squash to "selftests/bpf: Add mptcp sched structs" Geliang Tang
2023-05-27 12:55 ` [PATCH mptcp-next 8/8] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-05-27 15:28 ` MPTCP CI [this message]
2023-05-28 16:37 ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-11-11 7:48 [PATCH mptcp-next v19 9/9] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-11-11 9:53 ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-11-16 2:38 ` MPTCP CI
2022-10-14 13:32 [PATCH mptcp-next v8 15/15] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-14 15:49 ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-10-12 4:40 [PATCH mptcp-next v7 12/12] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-12 6:08 ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-10-11 12:01 [PATCH mptcp-next v6 13/13] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-11 13:36 ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-10-09 15:45 [PATCH mptcp-next] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-09 17:24 ` Squash to "selftests/bpf: Add bpf_rr scheduler": 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=3ea4474b-df97-b641-4f4e-fb24b84570cf@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.