From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: fix race on unaccepted mptcp sockets: Tests Results
Date: Fri, 17 Jun 2022 11:57:26 +0000 [thread overview]
Message-ID: <de84002f-5c68-1d49-0e44-1761f60e0602@gmail.com> (raw)
In-Reply-To: <dd32766a57e98209da3257e9c68980a3b8727797.1655460262.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/6043371033591808
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6043371033591808/summary/summary.txt
- KVM Validation: debug:
- Unstable: 2 failed test(s): packetdrill_add_addr selftest_diag 🔴:
- Task: https://cirrus-ci.com/task/5480421080170496
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5480421080170496/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/aed85d6d96bd
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-17 11:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:05 [PATCH mptcp-net v3 0/6] mptcp: mp_fail related fixes Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 1/6] mptcp: fix error mibs accounting Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 2/6] mptcp: introduce MAPPING_BAD_CSUM Paolo Abeni
2022-06-17 23:13 ` Mat Martineau
2022-06-20 9:24 ` Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 3/6] Squash-to: "mptcp: invoke MP_FAIL response when needed" Paolo Abeni
2022-06-17 14:01 ` Paolo Abeni
2022-06-17 23:06 ` Mat Martineau
2022-06-17 10:05 ` [PATCH mptcp-net v3 4/6] mptcp: fix shutdown vs fallback race Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 5/6] mptcp: consistent map handling on failure Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 6/6] mptcp: fix race on unaccepted mptcp sockets Paolo Abeni
2022-06-17 11:57 ` MPTCP CI [this message]
2022-06-18 0:51 ` Mat Martineau
2022-06-20 10:15 ` Paolo Abeni
2022-06-20 10:47 ` Paolo Abeni
2022-06-17 23:05 ` [PATCH mptcp-net v3 0/6] mptcp: mp_fail related fixes Mat Martineau
-- strict thread matches above, loose matches on Subject: below --
2022-06-21 17:23 [PATCH v5 mptcp-net 6/6] mptcp: fix race on unaccepted mptcp sockets Paolo Abeni
2022-06-21 18:58 ` mptcp: fix race on unaccepted mptcp sockets: Tests Results MPTCP CI
2022-06-20 11:26 [PATCH mptcp-net v4 6/6] mptcp: fix race on unaccepted mptcp sockets Paolo Abeni
2022-06-20 14:16 ` mptcp: fix race on unaccepted mptcp sockets: Tests Results MPTCP CI
2022-06-15 20:28 [PATCH mptcp-net v2 6/6] mptcp: fix race on unaccepted mptcp sockets Paolo Abeni
2022-06-15 22:10 ` mptcp: fix race on unaccepted mptcp sockets: 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=de84002f-5c68-1d49-0e44-1761f60e0602@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).