From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Christopher Li <sparse@chrisli.org>
Subject: [PATCH 1/3] testsuite: add tag to ignore the output/error
Date: Thu, 10 Nov 2016 15:45:18 +0100 [thread overview]
Message-ID: <20161110144520.24965-2-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20161110144520.24965-1-luc.vanoostenryck@gmail.com>
Currently the test suite always check the exit value and the output
of the command used for the test. This is fine and allow use to catch
the most common situations:
- failure or crash (via the exit value)
- (un)expected output (like when testing the result of the preprocessor)
- (un)expected errors & warnings (like when testing sparse's warnings)
But sometimes, we're not interested in the output or the output (as is)
is simply not meaningful for the test or can't be compared textually
to some reference.
This patch add two new tags (check-output-ignore & check-error-ignore),
telling to test suite to ignore the content of stdout or stderr when
testing this file.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
Documentation/test-suite | 6 ++++++
validation/test-suite | 2 ++
2 files changed, 8 insertions(+)
diff --git a/Documentation/test-suite b/Documentation/test-suite
index 6c4f24f6..6936feeb 100644
--- a/Documentation/test-suite
+++ b/Documentation/test-suite
@@ -29,6 +29,12 @@ check-output-start / check-output-end (optional)
The expected output (stdout and stderr) of check-command lies between
those two tags. It defaults to no output.
+check-output-ignore / check-error-ignore (optional)
+ Don't check the expected output (stdout or stderr) of check-command
+ (usefull when this output is not comparable or if you're only interested
+ in the exit value).
+ By default this check is done.
+
check-known-to-fail (optional)
Mark the test as being known to fail.
diff --git a/validation/test-suite b/validation/test-suite
index df5a7c60..0d874e07 100755
--- a/validation/test-suite
+++ b/validation/test-suite
@@ -146,6 +146,8 @@ do_test()
actual_exit_value=$?
for stream in output error; do
+ grep -s -q "check-$stream-ignore" $file && continue
+
diff -u "$file".$stream.expected "$file".$stream.got > "$file".$stream.diff
if [ "$?" -ne "0" ]; then
error "actual $stream text does not match expected $stream text."
--
2.10.1
next prev parent reply other threads:[~2016-11-10 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 14:45 [PATCH 0/3] fix discarded label statement Luc Van Oostenryck
2016-11-10 14:45 ` Luc Van Oostenryck [this message]
2016-11-17 17:15 ` [PATCH 1/3] testsuite: add tag to ignore the output/error Christopher Li
2016-11-10 14:45 ` [PATCH 2/3] testsuite: check patterns presence or absence in output Luc Van Oostenryck
2016-11-10 14:45 ` [PATCH 3/3] fix discarded label statement Luc Van Oostenryck
2016-11-17 17:19 ` 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=20161110144520.24965-2-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).