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
139 $ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6
146 Running tests without using ``kunit.py run`` is also an important use case.
203 failed (as of 5.13). But ``kunit.py parse`` would, see below.
216 You can use ``kunit.py parse`` to parse dmesg for test output and print out
217 results in the same familiar format that ``kunit.py run`` does.
221 $ ./tools/testing/kunit/kunit.py parse /var/log/dmesg