Lines Matching full:run
15 kunit_tool addresses the problem of being able to run tests without needing a
18 compiles the kernel as a standalone Linux executable that can be run like any
33 to run independently, or if you want to use pre-defined test configs for
43 ./tools/testing/kunit/kunit.py run
49 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
51 - ``--timeout`` sets a maximum amount of time to allow tests to run.
63 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig
65 For a list of all the flags supported by kunit_tool, you can run:
69 ./tools/testing/kunit/kunit.py run --help
74 It's also possible to run just parts of the KUnit build process independently,
92 run the kernel and display the test results with the ``exec`` argument:
98 The ``run`` command which is discussed above is equivalent to running all three
115 ./tools/testing/kunit/kunit.py run --raw_output
122 ./tools/testing/kunit/kunit.py run --raw_output=kunit
135 This is very useful if you wish to run tests in a configuration not supported
141 It's possible to run only a subset of the tests built into a kernel by passing
142 a filter to the ``exec`` or ``run`` commands. For example, if you only wanted
143 to run KUnit resource tests, you could use:
147 ./tools/testing/kunit/kunit.py run 'kunit-resource*'
159 options, etc) that allow KUnit tests to be run on the specified
165 this flag is ignored) the tests will run via UML. Non-UML architectures,
166 e.g. i386, x86_64, arm, um, etc. Non-UML run on QEMU.
178 In many cases it is likely that you may want to run an architecture which is
179 not supported by the ``--arch`` flag, or you may want to just run KUnit tests
194 ./tools/testing/kunit/kunit.py run \
209 (``config``, ``build``, ``run``, etc) will have different supported
220 kernel (with the ``build`` or ``run`` commands). For example, to enable
225 allyesconfig``. This allows you to run as many tests as is possible,