Netdev List
 help / color / mirror / Atom feed
From: Hangbin Liu <hangbin.liu@linux.dev>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: [ANN] Containers to run Netdev CI tests locally
Date: Fri, 4 Sep 2026 19:44:38 +0800	[thread overview]
Message-ID: <apqvJmgi9ZKmDDrW@fedora> (raw)
In-Reply-To: <bf2cd349-7d1f-4ace-acb7-948dbeada200@kernel.org>

On Fri, Sep 04, 2026 at 10:33:18AM +0200, Matthieu Baerts wrote:
> Hi Hangbin,
> 
> On 04/09/2026 08:59, Hangbin Liu wrote:
> > Hi Matthieu,
> > 
> > On Thu, Sep 03, 2026 at 06:19:25PM +0200, Matthieu Baerts wrote:
> >> 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
> > 
> > Great! I've been struggling to set up the local NIPA docker. I'm following
> > the steps from your git commit description. Now this article saved me.
> 
> I'm glad it helped!
> 

From a user‑experience perspective, I think the static tests work well.
They display the check results clearly and save outputs to the result directory.

However, for selftests, I do not see any difference compared to running vng
directly on my local machine, i.e.

  vng -v --run . --user root -a mitigations=off --cpus 4 -- \
  	make -C tools/testing/selftests TARGETS=net run_tests

Do you know how to make the result looks like the CI shows[1], that each test
has a separate log dir and shows stdout/stderr.

[1] https://netdev.bots.linux.dev/contest.html

Thanks
Hangbin

  reply	other threads:[~2026-09-04 11:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 16:19 [ANN] Containers to run Netdev CI tests locally Matthieu Baerts
2026-09-04  6:59 ` Hangbin Liu
2026-09-04  8:33   ` Matthieu Baerts
2026-09-04 11:44     ` Hangbin Liu [this message]
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
2026-09-08 15:56 ` Stanislav Fomichev
2026-09-08 16:25   ` Matthieu Baerts
2026-09-08 17:35     ` Stanislav Fomichev

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=apqvJmgi9ZKmDDrW@fedora \
    --to=hangbin.liu@linux.dev \
    --cc=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