From: Matthieu Baerts <matttbe@kernel.org>
To: Netdev <netdev@vger.kernel.org>
Subject: [ANN] Containers to run Netdev CI tests locally
Date: Thu, 3 Sep 2026 18:19:25 +0200 [thread overview]
Message-ID: <9c66a2b4-2787-4421-bc9b-627de2f708bd@kernel.org> (raw)
Hello,
TL;DR: containers are now available with all dependencies to easily
execute all static, unit, and functional tests in an environment closed
to the Netdev CI one:
- https://github.com/orgs/linux-netdev/packages
- https://github.com/linux-netdev/nipa/wiki/Running-Netdev-CI-tests-locally
-- ** -- ** --
As already mentioned on this list, and repeated at the last Netdev Conf,
developers are expected to validate the same tests as the ones executed
by the Netdev CI before any submissions. This includes all static, unit
and functional tests linked to the net subsystem -- and impacted by the
modifications --, but also LLM reviews. The goal is to reduce the number
of revisions and general traffic on this mailing list, not to overload
maintainers and reviewers even more.
A wiki page has been added to cover this and explain how to validate the
different tests:
https://github.com/linux-netdev/nipa/wiki/Running-Netdev-CI-tests-locally
To help developers, containers are now built, packing all the required
dependencies to run these tests in order to run the tests in an
environment that would be as close as possible to the CI one. The goal
is to have an environment that is easy to maintain -- no heavy
optimisations to reduce the images size -- but also easy to use. In
short, people (and non-humans) can continue to use the different tools
as before, but add a prefix to the different commands to execute them
from a container, e.g.
alias run="${nipa}/docker/selftests/run.sh"
run vng --build
run make headers
(...)
Feedback on this is welcome. Do not hesitate to report issues on the
GitHub project (or here) and share fixes!
Note: currently only 'docker' is supported, but 'podman' can be used,
and plain 'chroot' as well, see the wiki. Patches are welcome!
Also, the following page has been modified to include more tips, visual
improvements, and references to the new containers:
https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style
Cheers,
Matt
--
For the Netdev Foundation
next reply other threads:[~2026-09-03 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 16:19 Matthieu Baerts [this message]
2026-09-04 6:59 ` [ANN] Containers to run Netdev CI tests locally Hangbin Liu
2026-09-04 8:33 ` Matthieu Baerts
2026-09-04 11:44 ` Hangbin Liu
2026-09-04 17:29 ` Matthieu Baerts
2026-09-04 14:01 ` Ilya Maximets
2026-09-04 14:54 ` Matthieu Baerts
2026-09-04 15:25 ` Ilya Maximets
2026-09-04 16:17 ` Matthieu Baerts
2026-09-04 16:37 ` Ilya Maximets
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=9c66a2b4-2787-4421-bc9b-627de2f708bd@kernel.org \
--to=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
/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