Lines Matching refs:py

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
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
64 	$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
71 	$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit
97 	$ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false
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.
214 	failed (as of 5.13). But ``kunit.py parse`` would, see below.
227 You can use ``kunit.py parse`` to parse dmesg for test output and print out
228 results in the same familiar format that ``kunit.py run`` does.
232 	$ ./tools/testing/kunit/kunit.py parse /var/log/dmesg
333 KTAP format). Note that attributes will be hidden by default in kunit.py output
360 	kunit.py run "example" --list_tests_attr
374 	kunit.py run --filter speed=slow
382 	kunit.py run --filter "speed>slow"
393 	kunit.py run --filter "speed>slow, module=kunit_example_test"