From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: MPTCP CI: now validating stable versions
Date: Fri, 19 Dec 2025 19:01:59 +0100 [thread overview]
Message-ID: <04d68786-d421-4f8e-8f24-bd6893fff414@kernel.org> (raw)
Hello,
FYI, a new job has recently been added, validating stable versions:
https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/stable.yml
Results are visible in "flakes" webui + IRC (#mptcp-ci)
https://ci-results.mptcp.dev/flakes.html
You can see the different results by selecting a "Version" (top left),
e.g.
https://ci-results.mptcp.dev/flakes.html?branch=stable-6.12
It is using the stable patches that have been queued but not released
yet [1] + pending MPTCP ones available in our patchwork [2], with the
kernel version in the patch subject.
Note that once a week (Sunday), this job is using the selftests from the
'export' branch, e.g.
https://ci-results.mptcp.dev/flakes.html?branch=latest-6.12
It is important to keep in mind that some tests might be failing
because:
- tests are expecting a fix which has not been backported to stable yet,
especially when using the selftests from the export branch.
- there might be a behaviour change, but a modification is needed in
stable packetdrill branches, etc.
It looks important to fix (real) issues from stable in priority.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
[2] https://patchwork.kernel.org/project/mptcp/list/?state=*
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
reply other threads:[~2025-12-19 18:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=04d68786-d421-4f8e-8f24-bd6893fff414@kernel.org \
--to=matttbe@kernel.org \
--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