Hi Cyril, On Wed, Oct 16, 2024 at 9:11 AM Cyril Hrubis <chrubis@xxxxxxx> wrote: > > Hi! > > Just saying "LTP" is not granular enough. LTP has hundreds of individual > > test programs, and it would be useful to specify the individual tests > > from LTP that should be run per sub-system. > > A few thousand tests to be more precise, and also the content tend to > change between releases, be it test additions or removal and I do not > think this level of changes is somehing that makes sense to be tracked > in such database. > > It may be better to have more generic description of LTP subsets, there > are a few obvious e.g. "SysV IPC" or "Timers", and have the LTP > testrunner map that to actual testcases. The hard task here is to figure > out which groups would be useful and keep the set reasonably small. > > I can move this forward in LTP reasonably quickly we get small list of > useful groups from kernel develpers. Thanks! The thought was if we wanted to encourage contributors to run these tests before submitting, does running the whole LTP testsuite make sense or like you said a targeted set would be much better? Cheers, Don > > -- > Cyril Hrubis > chrubis@xxxxxxx >
