From: Eric Biggers <ebiggers@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: kernelci@lists.linux.dev
Subject: Re: Enabling additional KUnit tests in KernelCI?
Date: Thu, 12 Mar 2026 14:51:45 -0700 [thread overview]
Message-ID: <20260312215145.GA4805@quark> (raw)
In-Reply-To: <d2c55e92-5210-4d12-86f4-a24b64ab0fb9@sirena.org.uk>
On Thu, Mar 12, 2026 at 08:21:26PM +0000, Mark Brown wrote:
> On Fri, Mar 06, 2026 at 11:55:46PM -0800, Eric Biggers wrote:
>
> > I would like the KUnit tests in lib/crypto/tests/ and lib/crc/tests/ to
> > run in KernelCI and have any failures reported to
> > linux-crypto@vger.kernel.org. Preferably on all platforms, not just
> > UML, since UML doesn't cover all the code. Is there a way to do this?
> > What is the status of KUnit in KernelCI? I'm having a hard time finding
> > information about this, and looking at the latest mainline test results
> > (https://dashboard.kernelci.org/tree/mainline/master/4ae12d8bd9a830799db335ee661d6cbc6597f838?p=t)
> > there seem to be no KUnit tests running at all.
>
> We should be running KUnit tests:
>
> https://github.com/kernelci/kernelci-pipeline/blob/a3b622cfee641e26bed1906b29ed7065bee45921/config/jobs.yaml#L2153
>
> https://github.com/kernelci/kernelci-pipeline/blob/a3b622cfee641e26bed1906b29ed7065bee45921/config/scheduler.yaml#L1750
Which ones? Does anything need to be done to add new tests to the list?
Note that even if "all" tests are being run (via
CONFIG_KUNIT_ALL_TESTS=y), that includes only the tests whose
dependencies are met. There can be additional kconfig dependencies.
> though like you say something seems to be going AWOL with at least the
> reporting, I can't see any results either. The job that's configured
> there is to run on x86_64 rather than UML so is probably what you're
> looking for in terms of the tests?
The kernel has optimized crypto and/or CRC code for the following
architectures: arm, arm64, mips, powerpc, riscv, s390, sparc, x86. In
many cases there's also a finer division based on CPU features.
So I'm looking for testing on as many platforms as possible. But some
x86_64 platform is a good start, certainly better than nothing.
- Eric
next prev parent reply other threads:[~2026-03-12 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 7:55 Enabling additional KUnit tests in KernelCI? Eric Biggers
2026-03-12 20:21 ` Mark Brown
2026-03-12 21:51 ` Eric Biggers [this message]
2026-03-12 23:34 ` Mark Brown
2026-03-13 1:04 ` Eric Biggers
2026-03-13 12:31 ` Mark Brown
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=20260312215145.GA4805@quark \
--to=ebiggers@kernel.org \
--cc=broonie@kernel.org \
--cc=kernelci@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