Re: [PATCH] kern-devsrc: Drop auto.conf creation

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2022-08-09 at 10:22 -0400, Bruce Ashfield wrote:
> On Tue, Aug 9, 2022 at 10:08 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Tue, 2022-08-09 at 09:29 -0400, Bruce Ashfield wrote:
> > > On Tue, Aug 9, 2022 at 9:26 AM Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > > 
> > > > On Tue, 2022-08-09 at 09:16 -0400, Bruce Ashfield wrote:
> > > > > On Tue, Aug 9, 2022 at 7:14 AM Richard Purdie
> > > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > > > 
> > > > > > After this commit in the mainline kernel, the quoting is different in auto.conf
> > > > > > compared to .config:
> > > > > > 
> > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=129ab0d2d9f38b9d43df35235fc66c6740d6928b
> > > > > > 
> > > > > > We therefore can't just copy one over the other or it leads to syntax/quoting
> > > > > > errors. We end up running make prepare anyway in all our tests so drop
> > > > > > this copy for fix 5.19 kernels.
> > > > > 
> > > > > It is safe to stop doing this manipulation now.
> > > > > 
> > > > > But I am curious, I was running on-target tests for 5.19+ and didn't
> > > > > have any issues, what is breaking that I managed to miss ?
> > > > 
> > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/5629/steps/13/logs/stdio
> > > > 
> > > > Basically any kernelmodule.KernelModuleTest.test_kernel_module which
> > > > was run was failing (which would run on any image with kernel-devsrc in
> > > > and a toolchain). It failed everywhere, all sdk qemu machines equally.
> > > 
> > > odd. I never did see that same error, and I built and installed kernel
> > > module for all the architectures.
> > 
> > Did you use the oeqa code or something else? It seems odd you didn't
> > see it as it was quite consistent on my local system and the
> > autobuilders :/
> 
> I run everything by hand, oeqa has always taken too long in my
> infrastructure, so I run the kernel tests myself.

You could do something like:

IMAGE_CLASSES += "testimage"
TEST_SUTITES = "ping ssh kernelmodule"

and then

bitbake core-image-sato-sdk
bitbake core-image-sato-sdk -c testimage

just to run that one.

(I might have missed a test dependency which would need to be added to
the list in TEST_SUITES but you get the idea)

Cheers,

Richard