From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: tcp: allow again tcp_disconnect() when threads are waiting: Tests Results
Date: Mon, 09 Oct 2023 15:59:32 +0000 [thread overview]
Message-ID: <8710cbea-b1a2-41bf-2099-c827d10d2407@gmail.com> (raw)
In-Reply-To: <1d0e4528ab057a246fd8c60b91cffd34f277b957.1696848602.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 (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5338936801755136
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5338936801755136/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/6183361731887104
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6183361731887104/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5057461825044480
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5057461825044480/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6464836708597760
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6464836708597760/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/75398488591a
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-10-09 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 14:37 [PATCH net] tcp: allow again tcp_disconnect() when threads are waiting Paolo Abeni
2023-10-09 15:59 ` MPTCP CI [this message]
2023-10-10 15:50 ` Mat Martineau
2023-10-10 16:21 ` Eric Dumazet
2023-10-10 16:45 ` Paolo Abeni
2023-10-10 17:40 ` Paolo Abeni
2023-10-10 17:04 ` tcp: allow again tcp_disconnect() when threads are waiting: Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2023-10-11 7:20 [PATCH v2 net] tcp: allow again tcp_disconnect() when threads are waiting Paolo Abeni
2023-10-11 8:31 ` tcp: allow again tcp_disconnect() when threads are waiting: 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=8710cbea-b1a2-41bf-2099-c827d10d2407@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