From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Subject: Re: DO-NOT-MERGE: mptcp: enabled by default
Date: Fri, 10 May 2024 13:10:40 +0200 [thread overview]
Message-ID: <71912cc4-06b7-490a-bed6-ce50424f282e@kernel.org> (raw)
In-Reply-To: <3f59cd64-1d30-178b-7328-a59320b7d0f5@gmail.com>
Hello,
On 09/05/2024 21:00, MPTCP CI wrote:
> Hi Matthieu,
>
> Thank you for your modifications, that's great!
>
> Our CI did some validations and here is its report:
>
> - KVM Validation: normal: Success! ✅
> - KVM Validation: debug: Unstable: 1 failed test(s): selftest_mptcp_join 🔴
> - KVM Validation: btf (only bpftest_all): Success! ✅
> - Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/9021747950
>
> Initiator: Matthieu Baerts (NGI0)
> Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/5506cb76c43e
> Patchwork:
FYI, this is due to Patchew trying to apply patches that are already in
the tree, and ended up pushing the non modified export branch in a new
tag because 'git am' didn't do anything but didn't complain.
I just added a workaround to (hopefully) avoid doing such builds and
send useless notifications.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-05-10 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 19:00 DO-NOT-MERGE: mptcp: enabled by default MPTCP CI
2024-05-10 11:10 ` Matthieu Baerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 18:52 MPTCP CI
2024-04-10 10:40 MPTCP CI
2024-04-05 13:58 MPTCP CI
2024-03-13 13:12 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=71912cc4-06b7-490a-bed6-ce50424f282e@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).