On Fri, Feb 5, 2021 at 4:09 PM Daniel Latypov <dlatypov@xxxxxxxxxx> wrote: > > When using `kunit.py run` to run tests, users must populate a > `kunitconfig` file to select the options the tests are hidden behind and > all their dependencies. > > The patch [1] to allow specifying a path to kunitconfig promises to make > this nicer as we can have checked in files corresponding to different > sets of tests. > > But it's still annoying > 1) when trying to run a subet of tests > 2) when you want to run tests that don't have such a pre-existing > kunitconfig and selecting all the necessary options is tricky. > > This patch series aims to alleviate both: > 1) `kunit.py run 'my-suite-*'` > I.e. use my current kunitconfig, but just run suites that match this glob > 2) `kunit.py run --alltests 'my-suite-*'` > I.e. use allyesconfig so I don't have to worry about writing a > kunitconfig at all. > > See the first commit message for more details and discussion about > future work. > > This patch series also includes a bugfix for a latent bug that can't be > triggered right now but has worse consequences as a result of the > changes needed to plumb in this suite name glob. > > [1] https://lore.kernel.org/linux-kselftest/20210201205514.3943096-1-dlatypov@xxxxxxxxxx/ Tested-by: Brendan Higgins <brendanhiggins@xxxxxxxxxx>
