From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags: Tests Results
Date: Wed, 29 Jun 2022 22:55:09 +0000 [thread overview]
Message-ID: <15ca1394-b763-d8e0-9625-83825a6532c1@gmail.com> (raw)
In-Reply-To: <20220629223550.655928-3-mathew.j.martineau@linux.intel.com>
Hi Mat,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- {"code":404,"message":
- "Can't find artifacts containing file conclusion.txt"}:
- Task: https://cirrus-ci.com/task/4719806531239936
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4719806531239936/summary/summary.txt
- {"code":404,"message":
- "Can't find artifacts containing file conclusion.txt"}:
- Task: https://cirrus-ci.com/task/5845706438082560
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5845706438082560/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/2c27d7a3c28d
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-29 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 22:35 [PATCH mptcp-net v2 0/2] Locking fixes for subflow flag changes Mat Martineau
2022-06-29 22:35 ` [PATCH mptcp-net v2 1/2] mptcp: Avoid acquiring PM lock for subflow priority changes Mat Martineau
2022-06-29 22:47 ` Mat Martineau
2022-06-29 22:35 ` [PATCH mptcp-net v2 2/2] mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags Mat Martineau
2022-06-29 22:42 ` mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags: Build Failure MPTCP CI
2022-06-29 22:55 ` MPTCP CI [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-29 22:53 [PATCH mptcp-net v3 2/2] mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags Mat Martineau
2022-06-30 0:44 ` mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags: Tests Results MPTCP CI
2022-06-28 19:03 [PATCH mptcp-net 3/3] mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags Mat Martineau
2022-06-28 20:50 ` mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags: 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=15ca1394-b763-d8e0-9625-83825a6532c1@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=mathew.j.martineau@linux.intel.com \
--cc=mptcp@lists.linux.dev \
/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).