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_first test": Tests Results
Date: Tue, 17 May 2022 08:06:16 +0000 [thread overview]
Message-ID: <cf46e135-ea3e-362f-bee3-90a14f74ab10@gmail.com> (raw)
In-Reply-To: <4ec9eedaed38a5ae4b5bf04320ab5b6bcab8dba9.1652773325.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: Script error! ❓:
- :
- Task: https://cirrus-ci.com/task/5549153072709632
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5549153072709632/summary/summary.txt
- KVM Validation: Script error! ❓:
- :
- Task: https://cirrus-ci.com/task/6675052979552256
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6675052979552256/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/4eee192e015b
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:[~2022-05-17 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 7:43 [PATCH mptcp-next] Squash to "bpf: add bpf_skc_to_mptcp_sock_proto" Geliang Tang
2022-05-17 7:43 ` [PATCH mptcp-next] Squash to "selftests/bpf: add MPTCP test base" Geliang Tang
2022-05-17 7:43 ` [PATCH mptcp-next] Squash to "selftests/bpf: test bpf_skc_to_mptcp_sock" Geliang Tang
2022-05-17 7:43 ` [PATCH mptcp-next] Squash to "selftests/bpf: verify token of struct mptcp_sock" Geliang Tang
2022-05-17 7:43 ` [PATCH mptcp-next] Squash to "selftests/bpf: verify ca_name " Geliang Tang
2022-05-17 7:43 ` [PATCH mptcp-next] Squash to "selftests/bpf: verify first " Geliang Tang
2022-05-17 7:43 ` [PATCH mptcp-next] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-05-17 8:06 ` MPTCP CI [this message]
2022-05-17 8:07 ` Squash to "bpf: add bpf_skc_to_mptcp_sock_proto": Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2022-05-19 8:25 [PATCH mptcp-next v2] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-05-19 10:49 ` Squash to "selftests/bpf: add bpf_first test": Tests Results MPTCP CI
2022-06-09 5:23 [PATCH mptcp-next] Squash to "selftests/bpf: Add bpf_first test" Geliang Tang
2022-06-09 6:46 ` Squash to "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=cf46e135-ea3e-362f-bee3-90a14f74ab10@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