summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUlf Magnusson <ulfalizer@gmail.com>2017-09-18 10:12:56 +0200
committerGitHub <noreply@github.com>2017-09-18 10:12:56 +0200
commit0c6464ea783436b09379ee9e2c613e5d0d1c61d9 (patch)
tree9f6da692b7d70bc16bba3b565ebf61f1275517cd
parentdb419a89ff5e71f9e9f985fe7af548e0b9845e76 (diff)
Add note on running tests with older kernls
-rw-r--r--README.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/README.md b/README.md
index 14201d3..f61dafc 100644
--- a/README.md
+++ b/README.md
@@ -91,6 +91,11 @@ compare (character for character) configurations generated by Kconfiglib with
configurations generated by <i>scripts/kconfig/conf</i> for a number of cases. You
might want to use the "speedy" option; see [testsuite.py](testsuite.py).
+The test suite might fail for a few configurations for kernels older than April 2006,
+when a fix was added to Kconfig that's also mirrored in Kconfiglib (see 35ea8d5).
+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.