diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-11-18 11:57:55 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-11-18 11:57:55 -0800 |
| commit | f86fee1845eec29bed735e7120e6993ad8c4e295 (patch) | |
| tree | deea8ce84e2b7f8184f2f324176a14da4a1541e8 /Documentation/dev-tools/kunit/faq.rst | |
| parent | 0fa8ee0d9ab95c9350b8b84574824d9a384a9f7d (diff) | |
| parent | 3084db0e0d5076cd48408274ab0911cd3ccdae88 (diff) | |
| download | linux-next-f86fee1845eec29bed735e7120e6993ad8c4e295.tar.gz linux-next-f86fee1845eec29bed735e7120e6993ad8c4e295.zip | |
Merge tag 'linux-kselftest-kunit-fixes-5.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
Pull Kunit fixes from Shuah Khan:
"Several fixes to Kunit documentation and tools, and to not pollute
the source directory.
Also remove the incorrect kunit .gitattributes file"
* tag 'linux-kselftest-kunit-fixes-5.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
kunit: fix display of failed expectations for strings
kunit: tool: fix extra trailing \n in raw + parsed test output
kunit: tool: print out stderr from make (like build warnings)
KUnit: Docs: usage: wording fixes
KUnit: Docs: style: fix some Kconfig example issues
KUnit: Docs: fix a wording typo
kunit: Do not pollute source directory with generated files (test.log)
kunit: Do not pollute source directory with generated files (.kunitconfig)
kunit: tool: fix pre-existing python type annotation errors
kunit: Fix kunit.py parse subcommand (use null build_dir)
kunit: tool: unmark test_data as binary blobs
Diffstat (limited to 'Documentation/dev-tools/kunit/faq.rst')
| -rw-r--r-- | Documentation/dev-tools/kunit/faq.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/dev-tools/kunit/faq.rst b/Documentation/dev-tools/kunit/faq.rst index 1628862e7024..8d5029ad210a 100644 --- a/Documentation/dev-tools/kunit/faq.rst +++ b/Documentation/dev-tools/kunit/faq.rst @@ -90,7 +90,7 @@ things to try. re-run kunit_tool. 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This may help clean up any residual config items which could be causing problems. -6. Finally, try running KUnit outside UML. KUnit and KUnit tests can run be +6. Finally, try running KUnit outside UML. KUnit and KUnit tests can be built into any kernel, or can be built as a module and loaded at runtime. Doing so should allow you to determine if UML is causing the issue you're seeing. When tests are built-in, they will execute when the kernel boots, and |