diff options
| author | Ulf Magnusson <ulfalizer@gmail.com> | 2017-11-07 12:29:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-07 12:29:51 +0100 |
| commit | a1ae4e38503eb8a55712b6cd1f9d958035b0fd38 (patch) | |
| tree | f5ecedf16dcca67100eba97445bff72d16240bc3 | |
| parent | 2294a0d3822062ef42b073b1b482b0856a06313b (diff) | |
Clean up the test suite section a bit
| -rw-r--r-- | README.rst | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -313,12 +313,13 @@ The test suite is run with $ python(3) Kconfiglib/testsuite.py -(`pypy <http://pypy.org>`_ works too, and is much speedier.) +(`pypy <http://pypy.org>`_ works too, and is much speedier for everything except ``allnoconfig.py``/``allnoconfig_simpler.py``/``allyesconfig.py``, where it doesn't have time to warm up since +the scripts are run via ``make scriptconfig``.) -The test suite must be run from the top-level kernel directory. It requires that the git -repository has been cloned into it and that ``makefile.patch`` has been applied. +The test suite must be run from the top-level kernel directory, and requires that the git +repository has been cloned into it and that the makefile patch has been applied. -**NOTE: Some tests currently overwrite .config in the kernel root, so make sure to back it up.** +**NOTE: The test suite overwrites .config in the kernel root, so make sure to back it up.** The test suite consists of a set of selftests and a set of compatibility tests that compare (character for character) configurations generated by Kconfiglib with @@ -332,9 +333,8 @@ when a fix was added to Kconfig that's also mirrored in Kconfiglib This is harmless, and only counts as a fail since the test suite compares literal output from the kconfig version that's bundled with the kernel. -Kconfiglib is much faster than the test suite would indicate. Most of the time -is spent waiting around for ``make`` or the C utilities. Adding some multiprocessing -to the test suite would make sense. +A lot of the time is spent waiting around for ``make`` and the C utilities (which need to reparse all the +Kconfig files for each defconfig test). Adding some multiprocessing to the test suite would make sense. Notes ----- |