From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: bpf: add skc_to_mptcp_sock test: Tests Results
Date: Sun, 06 Mar 2022 01:48:46 +0000 [thread overview]
Message-ID: <36be94ec-10ef-80dc-46eb-ba25a0ba00a1@gmail.com> (raw)
In-Reply-To: <f1b08465b87273f458eaa67df848453fc0e25413.1646528337.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:
- {"code":404,"message":
- "HTTP 404 Not Found"}:
- Task: https://cirrus-ci.com/task/6291582512005120
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6291582512005120/summary/summary.txt
- {"code":404,"message":
- "HTTP 404 Not Found"}:
- Task: https://cirrus-ci.com/task/5386436542201856
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5386436542201856/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/5890857c7ca9
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-03-06 1:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 1:01 [PATCH mptcp-next v6 0/4] add skc_to_mptcp_sock Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 1/4] Revert "selftests: bpf: add bpf_mptcp_sock() verifier tests" Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 2/4] Revert "bpf: add 'bpf_mptcp_sock' structure and helper" Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 3/4] bpf: add skc_to_mptcp_sock helper Geliang Tang
2022-03-07 14:04 ` Matthieu Baerts
2022-03-07 14:29 ` Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 4/4] selftests: bpf: add skc_to_mptcp_sock test Geliang Tang
2022-03-06 1:48 ` selftests: bpf: add skc_to_mptcp_sock test: Tests Results MPTCP CI
2022-03-06 1:48 ` MPTCP CI [this message]
2022-03-07 12:27 ` MPTCP CI
2022-03-07 14:15 ` [PATCH mptcp-next v6 4/4] selftests: bpf: add skc_to_mptcp_sock test Matthieu Baerts
2022-03-07 15:58 ` Geliang Tang
2022-03-07 16:15 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-03-08 4:02 [PATCH mptcp-next v7 " Geliang Tang
2022-03-08 5:32 ` selftests: bpf: add skc_to_mptcp_sock test: Tests Results MPTCP CI
2022-03-08 10:47 [PATCH mptcp-next v8 5/5] selftests: bpf: add skc_to_mptcp_sock test Geliang Tang
2022-03-08 11:56 ` selftests: bpf: add skc_to_mptcp_sock test: Tests Results MPTCP CI
2022-03-08 13:16 [PATCH mptcp-next v9 5/5] selftests: bpf: add skc_to_mptcp_sock test Geliang Tang
2022-03-08 14:38 ` selftests: bpf: add skc_to_mptcp_sock 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=36be94ec-10ef-80dc-46eb-ba25a0ba00a1@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.