From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: add mptcp_lib_events helper: Tests Results
Date: Thu, 22 Feb 2024 04:31:29 +0000 [thread overview]
Message-ID: <6e66369e-cbca-3de2-8629-abdf288e055b@gmail.com> (raw)
In-Reply-To: <a306733bbc030878afda1ba501a94b40b92ec264.1708572320.git.tanggeliang@kylinos.cn>
Hi Geliang,
Thank you for your modifications, that's great!
Our CI (GitHub Action) did some validations and here is its report:
- KVM Validation: normal:
- Unstable: 1 failed test(s): packetdrill_regressions 🔴:
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/7999199133
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/965ac86521bd
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-normal
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-02-22 4:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 3:40 [PATCH mptcp-next v4 0/4] add helpers and vars in mptcp_lib.sh, part 2 Geliang Tang
2024-02-22 3:40 ` [PATCH mptcp-next v4 1/4] selftests: mptcp: add local variables rndh Geliang Tang
2024-02-22 3:40 ` [PATCH mptcp-next v4 2/4] selftests: mptcp: add mptcp_lib_ns_init/exit helpers Geliang Tang
2024-02-22 10:34 ` Matthieu Baerts
2024-02-22 3:40 ` [PATCH mptcp-next v4 3/4] selftests: mptcp: more operations in ns_init/exit Geliang Tang
2024-02-22 3:40 ` [PATCH mptcp-next v4 4/4] selftests: mptcp: add mptcp_lib_events helper Geliang Tang
2024-02-22 4:31 ` MPTCP CI [this message]
2024-02-22 11:07 ` Matthieu Baerts
2024-02-22 11:15 ` Matthieu Baerts
2024-02-22 10:30 ` [PATCH mptcp-next v4 0/4] add helpers and vars in mptcp_lib.sh, part 2 Matthieu Baerts
2024-02-22 11:39 ` Matthieu Baerts
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=6e66369e-cbca-3de2-8629-abdf288e055b@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