From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: drop lookup_by_id parameter in lookup_addr: Tests Results
Date: Sat, 04 Nov 2023 09:56:31 +0000 [thread overview]
Message-ID: <72cd87f6-a280-6965-6263-ef220e326e05@gmail.com> (raw)
In-Reply-To: <ac3acaec649cf088b9aef476f7d8e0ec38d62ac8.1699086244.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/5715754092331008
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5715754092331008/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5152804138909696
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5152804138909696/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6278704045752320
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6278704045752320/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Critical: 3 Call Trace(s) ❌:
- Task: https://cirrus-ci.com/task/4871329162199040
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4871329162199040/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/5c73e0a6e105
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-11-04 9:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 8:35 [PATCH mptcp-next v3 00/12] add flush and dump for userspace pm Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 01/12] mptcp: export pm_nl_get_pernet_from_msk Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 02/12] mptcp: use pernet id_bitmap in userspace pm Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 03/12] mptcp: rename free_local_addr_list with prefix Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 04/12] mptcp: flush userspace pm addrs list Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 05/12] mptcp: lookup_addr_by_id helper in userspace pm Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 06/12] mptcp: dump userspace pm addrs Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 07/12] mptcp: check userspace pm subflow flag Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 08/12] selftests: mptcp: add " Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 09/12] selftests: mptcp: flush and dump userspace addrs list Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 10/12] mptcp: drop mptcp_pm_get_* helpers Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 11/12] mptcp: add addresses_identically_equal helper Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v3 12/12] mptcp: drop lookup_by_id parameter in lookup_addr Geliang Tang
2023-11-04 9:56 ` MPTCP CI [this message]
2023-11-04 8:35 ` [PATCH mptcp-next v4 00/12] add refcount for address entry Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 01/12] mptcp: add userspace_pm_get_entry helper Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 02/12] mptcp: dup an entry when removing it Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 03/12] mptcp: add userspace pm addr entry refcount Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 04/12] selftests: mptcp: rm userspace addr with random order Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 05/12] mptcp: add netlink pm addr entry refcount Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 06/12] mptcp: drop addr_match and id_match Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 07/12] selftests: mptcp: add mptcp_lib_evts_* Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 08/12] selftests: mptcp: userspace: print colored results Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 09/12] selftests: mptcp: export event macros in mptcp_lib Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 10/12] selftests: mptcp: extract mptcp_lib_check_expected Geliang Tang
2023-11-04 8:35 ` [PATCH mptcp-next v4 11/12] selftests: mptcp: add mptcp_lib_verify_listener_events Geliang Tang
2023-11-04 8:36 ` [PATCH mptcp-next v4 12/12] selftests: mptcp: add mptcp_lib_init_ns Geliang Tang
2023-11-06 22:13 ` selftests: mptcp: add mptcp_lib_init_ns: Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 14:16 [PATCH mptcp-next v4 12/12] mptcp: drop lookup_by_id parameter in lookup_addr Geliang Tang
2023-11-04 15:31 ` mptcp: drop lookup_by_id parameter in lookup_addr: Tests Results MPTCP CI
2023-11-04 0:26 [PATCH mptcp-next v2 12/12] mptcp: drop lookup_by_id parameter in lookup_addr Geliang Tang
2023-11-04 1:43 ` mptcp: drop lookup_by_id parameter in lookup_addr: 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=72cd87f6-a280-6965-6263-ef220e326e05@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.