From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: fix checksum byte order: Tests Results
Date: Tue, 10 May 2022 18:36:43 +0000 [thread overview]
Message-ID: <cfbceaf4-fd14-c7dd-08af-9bf7e5d8ad45@gmail.com> (raw)
In-Reply-To: <595f104803a212df58db6d20f84947325b33a9d6.1652196378.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:
- Unstable: 1 failed test(s): selftest_simult_flows 🔴:
- Task: https://cirrus-ci.com/task/5103936225935360
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5103936225935360/summary/summary.txt
- KVM Validation: debug:
- Unstable: 1 failed test(s): selftest_diag 🔴:
- Task: https://cirrus-ci.com/task/5208863484936192
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5208863484936192/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/eb65d5350700
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-05-10 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 16:25 [PATCH mptcp-next v2] mptcp: fix checksum byte order Paolo Abeni
2022-05-10 18:36 ` MPTCP CI [this message]
2022-05-10 23:10 ` Mat Martineau
2022-05-11 10:22 ` Paolo Abeni
2022-05-11 15:22 ` Mat Martineau
2022-05-14 17:26 ` Matthieu Baerts
2022-05-16 23:07 ` Mat Martineau
2022-05-19 14:13 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-05-05 15:09 [PATCH MPTCP-next] " Paolo Abeni
2022-05-05 16:33 ` mptcp: fix checksum byte order: 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=cfbceaf4-fd14-c7dd-08af-9bf7e5d8ad45@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