Re: [PATCH 1/1] ltp: upgrade 20250530 -> 20250930

[Petr Vorel <petr.vorel@gmail.com>]

Hi Richard, all,

[ I accidentally deleted mail thread. Unfortunately I don't see Message-id in
web UI [1] therefore I cannot set In-Reply-To:. Due this also any reply to other
LTP developers about runltp vs. kirk would not be in the thread ]

> > $ . oe-init-build-env
> > 
> > .../build $ bitbake ltp
> > ERROR: Error importing OE modules: module 'bb.parse' has no attribute
> > 'vardepsexclude'
> > ERROR: Unable to parse
> > /home/pvorel/install/src/openembedded/bitbake/lib/bb/parse/ast.py
> > Traceback (most recent call last):
> >   File
> >   "/home/pvorel/install/src/openembedded/bitbake/lib/bb/parse/ast.py",
> >   line 372, in eval
> >       layerid, fragment_name = f.split('/', 1)
> > 	      ^^^^^^^^^^^^^^^^^^^^^^
> > 		  ValueError: not enough values to unpack (expected 2, got 1)
> > 

> > FYI I also plan to get rid of some patches posted.

> Are you setting OE_FRAGMENTS to something in a config file? It
> shouldn't traceback like this so that is a bug but something is
> triggering it...

No, simple clone and the 2 commands above. I'll later try it again on fresh
git clone.

> I did send some questions and had some discussion on kirk a while ago.
> Quite simply, it isn't useful/interesting to Yocto Project.

I see your points [2] [3].

> What we want to test with is our images and our kernel, as we build it.
> kirk, as far as I understand it has gone a different route where there
> isn't really any userspace left and it simply tests against a kernel
> binary. We'd no longer be testing our build artefacts but some more
> artificial construct.

I don't understand "any userspace left and it simply tests against a kernel
binary". LTP tests are mostly focused on the kernel (+ it's modules). And you
can run individual tests by just executing them (+ handle environment variables)
or use runltp or use kirk. The executor does not matter that much. In the end we
at SUSE also test with LTP our built image :). (LTP is used by mainline folks
and by distro folks).

FYI although kirk is meant to be run on the host, doing a different connections,
it can also be run on SUT. Sure, there is then python3 dependency on SUT
(heavier than shell + it's dependencies), but still kind of runltp replacement.

> 
> We're trying to test what we build. You're trying to test the kernel
> for regressions. They're two different things.
> 
> I totally understand why you've gone that direction with kirk but I
> also did spell out at the time that it wasn't something which really
> fits in with the way we run tests, or what we actually aim to test. I
> was told at the time that basically, nobody is interested in what we
> want/do.

...
> > I see in meta/lib/oeqa/runtime/cases/ltp.py the deprecated
> > /opt/ltp/runltp is still being used. We want to remove it (not sure
> > when, but it will happen sooner or later). Any change somebody would
> > submit a patch to switch to kirk?

> It is more likely that when you drop runltp, we'll just have to drop
> ltp. Sorry :(. I did explain this at while ago :/.

It's a question if any of the users really need LTP. If yes, you could vendor
runltp.

Or, write a simple script which parses the content of the runtest files and
execute them. FYI for part of openSUSE testing we still use our custom openQA
runner which does exactly this. It would be very light: -d and -r can be
replaced by TMPDIR and LTPROOT, -I is supported by all tests. The only missing
thing will be generating of results (if you really need it, I'd recommend kirk
and it's JSON output).

The reason we go to kirk + ltx is that in the future we plan to get rid of
runtests, replace them with metadata info (that will allow many things [4],
but you were Cc at the discussion [5]). Once this happen, runltp (or any custom
script / framework runner) will be broken. But this likely take long time.

> I did also flag the issue to our own wider community but nobody has
> stepped up to do anything about it. I've way too many other things to
> work on so it is very unlikely I have any time to look at it.

Understand, everybody is busy with the 

Kind regards,
Petr

[1] https://lists.openembedded.org/g/openembedded-core/message/224749
[2] https://lore.kernel.org/ltp/c8d4ee181809c4bbf5e21bf355c241eeb540e9a5.camel@linuxfoundation.org/
[3] https://lore.kernel.org/ltp/8043628a6eed94e788f9fedbf6c8b264ebfbae15.camel@linuxfoundation.org/
[4] https://www.youtube.com/watch?v=T1ImuNr9Oxo
[5] https://lore.kernel.org/ltp/ZmbFyjuXndeXCLp8@rei/