From: Guenter Roeck <linux@roeck-us.net>
To: Jakub Kicinski <kuba@kernel.org>
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 12:51:07 -0800 [thread overview]
Message-ID: <39a8176f-7c22-41ac-a027-dac10e349c51@roeck-us.net> (raw)
In-Reply-To: <f76d66dd-5920-4bf1-95f5-dd64f19826d4@roeck-us.net>
On 2/2/24 12:49, Guenter Roeck wrote:
> On 2/2/24 11:22, Jakub Kicinski wrote:
>> On Fri, 2 Feb 2024 09:21:22 -0800 Guenter Roeck wrote:
>>> when running handshake kunit tests in qemu, I always get the following
>>> failure.
>>
>> Sorry for sidetracking - how do you run kunit to get all the tests?
>> We run:
>>
>> ./tools/testing/kunit/kunit.py run --alltests
>>
>> but more and more I feel like the --alltests is a cruel joke.
>
> I have CONFIG_NET_HANDSHAKE_KUNIT_TEST=y enabled in my configuration.
> The tests run during boot, so no additional work is needed. I don't run all
> tests because many take too long to execute in qemu.
>
Follow-up: If this test isn't supposed to run during boot, please
let me know and I'll drop it.
Thanks,
Guenter
next prev parent reply other threads:[~2024-02-02 20:51 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 [this message]
2024-02-03 0:47 ` Jakub Kicinski
2024-02-03 1:45 ` Guenter Roeck
2024-02-03 2:27 ` Jakub Kicinski
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=39a8176f-7c22-41ac-a027-dac10e349c51@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).