From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: Squash-to: "selftests: mptcp: more stable diag tests": Tests Results
Date: Wed, 22 Jun 2022 11:52:11 +0000 [thread overview]
Message-ID: <4f2ad0c5-2667-c62c-b485-34923aa8bb28@gmail.com> (raw)
In-Reply-To: <f1109179c77a14bed80be75bb297aac1ef867a49.1655891188.git.pabeni@redhat.com>
Hi Paolo,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal:
- Success! ✅:
- Task: https://cirrus-ci.com/task/6497233930551296
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6497233930551296/summary/summary.txt
- KVM Validation: debug:
- Unstable: 2 failed test(s): selftest_mptcp_connect selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/5273199779774464
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5273199779774464/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/9c6d0fe8af73
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:[~2022-06-22 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 9:47 [PATCH mptcp-net] Squash-to: "selftests: mptcp: more stable diag tests" Paolo Abeni
2022-06-22 11:52 ` MPTCP CI [this message]
2022-06-22 21:10 ` Mat Martineau
2022-06-22 21:16 ` 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=4f2ad0c5-2667-c62c-b485-34923aa8bb28@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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 NNTP newsgroup(s).