[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3598f2c8-e04a-4e4a-ae1f-db2201fff802@t-8ch.de>
Date: Mon, 10 Mar 2025 19:22:35 +0100
From: Thomas Weißschuh <linux@...ssschuh.net>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: Willy Tarreau <w@....eu>, Shuah Khan <skhan@...uxfoundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] nolibc changes for v6.15
On 2025-03-10 10:09:49-0700, Paul E. McKenney wrote:
> On Sat, Mar 08, 2025 at 02:06:21PM +0100, Thomas Weißschuh wrote:
> > The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
> >
> > Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git tags/nolibc-20250308-for-6.15-1
> >
> > for you to fetch changes up to bceb73904c855c78402dca94c82915f078f259dd:
> >
> > tools/nolibc: don't use asm/ UAPI headers (2025-03-08 13:18:27 +0100)
>
> Thank you, I have pulled this in and will expose it to -next testing.
Thanks!
> Results from "make run":
>
> 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
>
> Results from "make user":
>
> 198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
>
> I don't understand the "warning" given that the "run.out" file has all
> "OK" aside from the two "SKIPPED" tests. Or maybe I am just forgetting
> how this works. ;-)
A skipped test will mark the whole run as "warning".
Maybe we'll adopt the kselftest harness at some point and align with the
rest of the selftests.
<snip>
Thomas
Powered by blists - more mailing lists