From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: join: use += operator to append strings: Tests Results
Date: Thu, 07 Mar 2024 15:07:01 +0000 [thread overview]
Message-ID: <b7feea40-7757-051e-695d-3f4a24c57520@gmail.com> (raw)
In-Reply-To: <c8bd786e0c09f4f19d518ec998a36f9fbd64e0b5.1709815545.git.tanggeliang@kylinos.cn>
Hi Geliang,
Thank you for your modifications, that's great!
Our CI (Cirrus) did some validations with a debug kernel and here is its report:
- KVM Validation: debug (except selftest_mptcp_join):
- Unstable: 1 failed test(s): packetdrill_regressions 🔴:
- Task: https://cirrus-ci.com/task/6379905680670720
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6379905680670720/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/4972530797117440
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4972530797117440/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/43ce1abbfb36
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 (NGI0 Core)
next prev parent reply other threads:[~2024-03-07 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 12:48 [PATCH mptcp-next 0/5] add helpers and vars in mptcp_lib.sh, part 4 Geliang Tang
2024-03-07 12:48 ` [PATCH mptcp-next 1/5] selftests: mptcp: extract mptcp_lib_check_expected Geliang Tang
2024-03-07 14:47 ` Matthieu Baerts
2024-03-07 12:48 ` [PATCH mptcp-next 2/5] selftests: mptcp: add mptcp_lib_verify_listener_events Geliang Tang
2024-03-07 14:49 ` Matthieu Baerts
2024-03-07 12:48 ` [PATCH mptcp-next 3/5] selftests: mptcp: export event macros in mptcp_lib Geliang Tang
2024-03-07 14:53 ` Matthieu Baerts
2024-03-07 12:48 ` [PATCH mptcp-next 4/5] selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL Geliang Tang
2024-03-07 12:48 ` [PATCH mptcp-next 5/5] selftests: mptcp: join: use += operator to append strings Geliang Tang
2024-03-07 13:41 ` selftests: mptcp: join: use += operator to append strings: Tests Results MPTCP CI
2024-03-07 14:55 ` [PATCH mptcp-next 5/5] selftests: mptcp: join: use += operator to append strings Matthieu Baerts
2024-03-07 15:07 ` MPTCP CI [this message]
2024-03-07 14:45 ` [PATCH mptcp-next 0/5] add helpers and vars in mptcp_lib.sh, part 4 Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2024-03-08 5:57 [PATCH mptcp-next v2 7/7] selftests: mptcp: join: use += operator to append strings Geliang Tang
2024-03-08 7:01 ` selftests: mptcp: join: use += operator to append strings: Tests Results MPTCP CI
2024-03-08 8:00 ` 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=b7feea40-7757-051e-695d-3f4a24c57520@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).