From: Jakub Kicinski <kuba@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Chuck Lever <chuck.lever@oracle.com>,
kernel-tls-handshake@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: Persistent problem with handshake unit tests
Date: Fri, 2 Feb 2024 18:27:04 -0800 [thread overview]
Message-ID: <20240202182704.5950d631@kernel.org> (raw)
In-Reply-To: <2ad1ff9f-bf42-4a36-855f-8ae62931dd84@roeck-us.net>
On Fri, 2 Feb 2024 17:45:55 -0800 Guenter Roeck wrote:
> > I was wondering how do you discover the options. Periodically grep for
> > new possible KUNIT options added to the kernel? Have some script that
> > does it.
>
> "Periodically grep for > new possible KUNIT options added to the kernel"
>
> Exactly, and see what happens if I enable them to determine if they run
> fast and if they are stable enough to be enabled in a qemu test. I can not
> enable tests automatically because some just take too long to run...
Ugh, we have such a long way to go with kernel testing :(
At least I know I'm not missing an obvious trick, thanks for explaining!
next prev parent reply other threads:[~2024-02-03 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 17:21 Persistent problem with handshake unit tests Guenter Roeck
2024-02-02 19:22 ` Jakub Kicinski
2024-02-02 20:49 ` Guenter Roeck
2024-02-02 20:51 ` Guenter Roeck
2024-02-03 0:47 ` Jakub Kicinski
2024-02-03 1:45 ` Guenter Roeck
2024-02-03 2:27 ` Jakub Kicinski [this message]
2024-02-03 3:46 ` Chuck Lever III
2024-02-03 3:54 ` Guenter Roeck
2024-02-06 16:47 ` Chuck Lever
2024-02-06 17:55 ` Guenter Roeck
2024-02-06 19:05 ` Guenter Roeck
2024-02-06 19:07 ` Chuck Lever
2024-02-06 19:24 ` Guenter Roeck
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=20240202182704.5950d631@kernel.org \
--to=kuba@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).