From ba7179d93465c66338de83e2a553f6a982a4efa7 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Tue, 16 Jun 2015 03:57:40 +0200 Subject: The test suite must be run from the top-level kernel directory. --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 8084847..b48ce57 100644 --- a/README.md +++ b/README.md @@ -74,13 +74,15 @@ language has some dark corners. The test suite is run with $ python(3) Kconfiglib/testsuite.py + +It must be run from the top-level kernel directory. **NOTE: Some tests currently overwrite .config in the kernel root, so make sure to back it up.** -It consists of a set of selftests and a set of compatibility tests that compare -configurations generated by Kconfiglib with configurations generated by -scripts/kconfig/conf for a number of cases. You might want to use the -"speedy" option; see [testsuite.py](testsuite.py). +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 +configurations generated by scripts/kconfig/conf for a number of cases. You +might want to use the "speedy" option; see [testsuite.py](testsuite.py). 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 -- cgit v1.2.3