Re: [LTP] [RFC PATCH] API: Allow testing of kernel features in development

[Petr Vorel <pvorel@suse.cz>]

Hi all,

> Hello,

> Cyril Hrubis <chrubis@suse.cz> writes:

> > Hi!
> >> I would be even tempted to add this to the default syscalls runtest file
> >> but render the test resultless, e.g. replace the tst_res() and tst_brk()
> >> handlers in tst_res.c so that it will print only INFO messages.

> > And that would also allow us to have env variable switch that would
> > enable all tests for unrelased features, something as
> > LTP_ENABLE_UNRELASED or so. Also with that we can really just TCONF if
> > that variable is not set which would be much simpler.

> I worry this will cause extra work for people reviewing
> TCONFs. Obviously the meta-data can be used to avoid any issues. However
> few people have integrated that into their tooling and workflow yet.

Can we solve this to have the policy? I don't have preference between having
special foo-unstable (or foo-staging) runtest files or TCONF unless
LTP_ENABLE_UNRELASED

(If we chose the latter, we could add this info into -h, thus people could run
./foo -h | grep ... to catch this before running; there could be even --json to
print metadata in json, which would include this info).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp