From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: add pm_nl_set_endpoint helper: Tests Results
Date: Mon, 12 Jun 2023 09:39:02 +0000 [thread overview]
Message-ID: <6ea59696-bc1c-106f-cbfc-83da5a98ca58@gmail.com> (raw)
In-Reply-To: <54a3b69d83dc1e965202eca7ccfdd4927b68de2d.1686554287.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):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6547545413910528
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6547545413910528/summary/summary.txt
- {"code":404,"message":
- "Can't find artifacts containing file conclusion.txt"}:
- Task: https://cirrus-ci.com/task/5280908018712576
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5280908018712576/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5843857972133888
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5843857972133888/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/4717958065291264
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4717958065291264/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/d63870a84ebf
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-12 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 7:19 [PATCH mptcp-next v18 0/7] update userspace pm mptcp_info fields part 2 Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 1/7] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 2/7] selftests: mptcp: test userspace pm out of transfer Geliang Tang
2023-06-12 16:03 ` Matthieu Baerts
2023-06-12 7:19 ` [PATCH mptcp-next v18 3/7] selftests: mptcp: check subflow and addr infos Geliang Tang
2023-06-12 16:04 ` Matthieu Baerts
2023-06-12 7:19 ` [PATCH mptcp-next v18 4/7] selftests: mptcp: drop test_linkfail parameter Geliang Tang
2023-06-12 16:25 ` Matthieu Baerts
2023-06-12 7:19 ` [PATCH mptcp-next v18 5/7] selftests: mptcp: drop addr_nr_ns1/2 parameters Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 6/7] selftests: mptcp: drop sflags parameter Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 7/7] selftests: mptcp: add pm_nl_set_endpoint helper Geliang Tang
2023-06-12 9:39 ` MPTCP CI [this message]
2023-06-12 16:43 ` selftests: mptcp: add pm_nl_set_endpoint helper: Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2023-06-13 5:31 [PATCH mptcp-next v19 8/8] selftests: mptcp: add pm_nl_set_endpoint helper Geliang Tang
2023-06-13 6:31 ` selftests: mptcp: add pm_nl_set_endpoint helper: Tests Results MPTCP CI
2023-06-05 8:18 [PATCH mptcp-next v16 5/5] selftests: mptcp: add pm_nl_set_endpoint helper Geliang Tang
2023-06-05 9:53 ` selftests: mptcp: add pm_nl_set_endpoint helper: 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=6ea59696-bc1c-106f-cbfc-83da5a98ca58@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.