Lines Matching full:run

7 Using ``kunit.py run`` ("kunit tool")
18 	  ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run "$@" )
22 	Early versions of ``kunit.py`` (before 5.6) didn't work unless run from
28 ``kunit.py run`` accepts an optional glob argument to filter tests. The format
31 Say that we wanted to run the sysctl tests, we could do so via:
36 	$ ./tools/testing/kunit/kunit.py run 'sysctl*'
43 	$ ./tools/testing/kunit/kunit.py run 'sysctl*.*write*'
55 ``kunit.py run`` (along with ``build``, and ``config``) supports a
56 ``--kunitconfig`` flag. So if you have a set of tests that you want to run on a
64 	$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
71 	$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit
82 	files to make it possible to have a top-level config run tests from all
97 	$ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false
105 	versions of gcc 7 and up. You're likely to run into missing ``.gcda``
126 …$ ./tools/testing/kunit/kunit.py run --kunitconfig=.kunit/ --kunitconfig=tools/testing/kunit/confi…
139 	$ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6
147 …$ ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --kunitconfig=.kunit/ --kunitconfig=too…
157 Running tests without using ``kunit.py run`` is also an important use case.
162 the kernel, run the ``./linux`` binary), this section will focus on testing
169 When setting tests to ``=y``, the tests will run as part of boot and print
204 Then after booting into our kernel, we can run the test via
228 results in the same familiar format that ``kunit.py run`` does.
360 	kunit.py run "example" --list_tests_attr
374 	kunit.py run --filter speed=slow
382 	kunit.py run --filter "speed>slow"
384 This example will run all tests with speeds faster than slow. Note that the
393 	kunit.py run --filter "speed>slow, module=kunit_example_test"
399 Filtered tests will not run or show up in the test output. You can use the
401 shown in the test output in the test but will not run. To use this feature when