From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Upstream <mptcp@lists.linux.dev>,
Geliang Tang <geliang@kernel.org>
Subject: CI: MPTCP BPF tests are now validated
Date: Thu, 7 Mar 2024 14:59:14 +0100 [thread overview]
Message-ID: <47ca79ba-6212-42af-af25-46b6bdf94eb1@kernel.org> (raw)
Hello,
From today, the CI is now validating MPTCP BPF tests!
To be able to do that, I got some help from Geliang (thanks!) to update
the script used by the CI to launch these tests. I just did the wiring
to run these tests in a new job, in parallel to the other ones, and it
seems working:
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/8186843723
Please tell me if there are anything wrong with that (results,
notifications, summary, etc.)
@Geliang: it looks like the "burst" test is unstable. Do you mind
looking at that please?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next reply other threads:[~2024-03-07 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 13:59 Matthieu Baerts [this message]
2024-03-11 1:54 ` CI: MPTCP BPF tests are now validated Geliang Tang
2024-03-21 2:22 ` Geliang Tang
2024-03-25 2:21 ` Geliang Tang
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=47ca79ba-6212-42af-af25-46b6bdf94eb1@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@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).