From: Pekka Enberg <penberg@kernel.org>
To: linux-sparse@vger.kernel.org
Cc: "Pekka Enberg" <penberg@kernel.org>,
"Ben Pfaff" <blp@cs.stanford.edu>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Christopher Li" <sparse@chrisli.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: [PATCH v2] sparse: Reduce 'test-suite' run output
Date: Tue, 30 Aug 2011 22:24:16 +0300 [thread overview]
Message-ID: <1314732256-6113-1-git-send-email-penberg@kernel.org> (raw)
There's more than 100 tests in the validation test suite. That makes it
cumbersome to notice test breakage in because the results don't fit on single
page.
We don't expect to see most tests to pass so it's much more convenient to
only be verbose for failing test cases. This patch changes the
'test-suite' output to report progress on a single line unless a test case
fails.
Current master 'make check' output looks as follows:
Makefile:53: Your system does not have libxml, disabling c2xml
TEST preprocessor/preprocessor14.c ( Preprocessor #14)
error: actual output text does not match expected output text.
error: see preprocessor/preprocessor14.c.output.* for further investigation.
--- preprocessor/preprocessor14.c.output.expected 2011-08-26 05:47:22.000000000 +0000
+++ preprocessor/preprocessor14.c.output.got 2011-08-26 05:47:22.000000000 +0000
@@ -1,2 +1,2 @@
-
+,
info: test 'preprocessor/preprocessor14.c' is known to fail
TEST static-forward-decl.c ( static forward declaration)
error: actual error text does not match expected error text.
error: see static-forward-decl.c.error.* for further investigation.
--- static-forward-decl.c.error.expected 2011-08-26 05:47:22.000000000 +0000
+++ static-forward-decl.c.error.got 2011-08-26 05:47:22.000000000 +0000
@@ -0,0 +1 @@
+static-forward-decl.c:3:5: warning: symbol 'f' was not declared. Should it be static?
info: test 'static-forward-decl.c' is known to fail
TEST varargs1.c ( Varargs bogus warning regression test #1)
Out of 102 tests, 100 passed, 2 failed (2 of them are known to fail)
Cc: Ben Pfaff <blp@cs.stanford.edu>
Cc: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Cc: Christopher Li <sparse@chrisli.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Pekka Enberg <penberg@kernel.org>
---
- v1 -> v2: Fix non-terminal output formatting
validation/test-suite | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/validation/test-suite b/validation/test-suite
index 3c011c6..543a94a 100755
--- a/validation/test-suite
+++ b/validation/test-suite
@@ -94,8 +94,11 @@ do_test()
return 2
fi
test_name=$last_result
-
- echo " TEST $test_name ($file)"
+ if test -t 1; then
+ printf "\r TEST %-80s" "$file ($test_name)"
+ else
+ echo " TEST $test_name ($file)"
+ fi
# does the test provide a specific command ?
cmd=`eval echo $default_path/$default_cmd`
@@ -128,6 +131,7 @@ do_test()
for stream in output error; do
diff -u "$file".$stream.expected "$file".$stream.got > "$file".$stream.diff
if [ "$?" -ne "0" ]; then
+ echo ""
error "actual $stream text does not match expected $stream text."
error "see $file.$stream.* for further investigation."
cat "$file".$stream.diff
@@ -163,6 +167,7 @@ do_test_suite()
# prints some numbers
tests_nr=`expr $ok_tests + $ko_tests`
+ echo ""
echo -n "Out of $tests_nr tests, $ok_tests passed, $ko_tests failed"
echo " ($known_ko_tests of them are known to fail)"
if [ "$unhandled_tests" -ne "0" ]; then
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-08-30 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 19:24 Pekka Enberg [this message]
2011-08-31 0:42 ` [PATCH v2] sparse: Reduce 'test-suite' run output Christopher Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1314732256-6113-1-git-send-email-penberg@kernel.org \
--to=penberg@kernel.org \
--cc=blp@cs.stanford.edu \
--cc=j.neuschaefer@gmx.net \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.