[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ-ks9=imoiGnYuFj7V0M3j8ecFrNRvPXQj6cWsfnGNRQuVpEA@mail.gmail.com>
Date: Sat, 22 Mar 2025 09:30:38 -0400
From: Tamir Duberstein <tamird@...il.com>
To: Aditya Garg <gargaditya08@...e.com>
Cc: Kees Cook <kees@...nel.org>, Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>, Sergey Senozhatsky <senozhatsky@...omium.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] printf: add tests for generic FourCCs
On Sat, Mar 22, 2025 at 6:04 AM Aditya Garg <gargaditya08@...e.com> wrote:
>
> Hi
>
> > On 21 Mar 2025, at 8:22 PM, Tamir Duberstein <tamird@...il.com> wrote:
> >
> > On Fri, Mar 21, 2025 at 10:23 AM Aditya Garg <gargaditya08@...e.com> wrote:
> >>
> >>
> >> Can you give me some docs for running the Kunit tests? The patch is basically a port of the original version.
> >
> > I use:
> >
> > tools/testing/kunit/kunit.py run --arch arm64 --make_options LLVM=1 printf
> >
> > You can probably just use:
> >
> > tools/testing/kunit/kunit.py run printf
> >
> > It would also be useful to see raw output:
> >
> > tools/testing/kunit/kunit.py run printf —raw_output
>
>
> Here are the requested outputs:
>
> --------------------------------------------------------------------------------------------------------------------------------
> Failed test:
>
> [...]
OK, it's not great but no worse than before.
Acked-by: Tamir Duberstein <tamird@...il.com>
Powered by blists - more mailing lists