[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65b133e83f53e_225ba129414@willemb.c.googlers.com.notmuch>
Date: Wed, 24 Jan 2024 10:59:36 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: David Ahern <dsahern@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Hangbin Liu <liuhangbin@...il.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"netdev-driver-reviewers@...r.kernel.org" <netdev-driver-reviewers@...r.kernel.org>
Subject: Re: [ANN] net-next is OPEN
David Ahern wrote:
> On 1/23/24 8:20 AM, Jakub Kicinski wrote:
> > On Tue, 23 Jan 2024 16:45:55 +0800 Hangbin Liu wrote:
> >>> Over the merge window I spent some time stringing together selftest
> >>> runner for netdev: https://netdev.bots.linux.dev/status.html
> >>> It is now connected to patchwork, meaning there should be a check
> >>> posted to each patch indicating whether selftests have passed or not.
> >>
> >> Cool! Does it group a couple of patches together and run the tests or
> >> run for each patch separately?
> >
> > It groups all patches outstanding in patchwork (which build cleanly).
> > I'm hoping we could also do HW testing using this setup, so batching
> > is a must. Not 100% sure it's the right direction for SW testing but
> > there's one way to find out :)
> >
>
> Really cool. Thanks for spending time to make this happen.
Just to add to the choir: this is fantastic, thanks!
Hopefully it will encourage people to add kselftests, kunit tests or
other kinds that now get continuous coverage.
Going through the failing ksft-net series on
https://netdev.bots.linux.dev/status.html, all the tests I'm
responsible seem to be passing.
Powered by blists - more mailing lists