linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 3/5] testsuite: report as error tests known to fail but which succeed
Date: Wed,  2 Nov 2016 22:45:07 +0100	[thread overview]
Message-ID: <20161102214509.36571-4-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20161102214509.36571-1-luc.vanoostenryck@gmail.com>

Such situation may simply show that what was tested is now fixed
and that it's juste the test annotation which need to be adapted,
but can be a sign that something else is broken.

Reporting the exact result (failure/success, known-to-fail/expect-to-succeed)
make the testsuite more useful and allow to use more efficiently
git-bisect or other automated testing tools.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 validation/test-suite | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/validation/test-suite b/validation/test-suite
index df5a7c60..03421a24 100755
--- a/validation/test-suite
+++ b/validation/test-suite
@@ -161,15 +161,26 @@ do_test()
 		test_failed=1
 	fi
 
+	get_tag "check-known-to-fail" $file
+	if [ "$?" -eq "0" ]; then
+		must_fail=1
+		known_ko_tests=`expr $known_ko_tests + 1`
+	else
+		must_fail=0
+	fi
+
 	if [ "$test_failed" -eq "1" ]; then
 		ko_tests=`expr $ko_tests + 1`
-		get_tag "check-known-to-fail" $file
-		if [ "$?" -eq "0" ]; then
+		if [ "$must_fail" -eq "1" ]; then
 			echo "info: test '$file' is known to fail"
-			known_ko_tests=`expr $known_ko_tests + 1`
 		fi
 		return 1
 	else
+		if [ "$must_fail" -eq "1" ]; then
+			echo "info: test '$file' is known to fail but succeed!"
+			ko_tests=`expr $ko_tests + 1`
+			return 1
+		fi
 		ok_tests=`expr $ok_tests + 1`
 		return 0
 	fi
-- 
2.10.1


  parent reply	other threads:[~2016-11-02 21:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 21:45 [PATCH 0/5] tests & testsuite small improvements Luc Van Oostenryck
2016-11-02 21:45 ` [PATCH 1/5] testsuite: give a proper name to the 'binary-constant' test Luc Van Oostenryck
2016-11-17 10:19   ` Christopher Li
2016-11-02 21:45 ` [PATCH 2/5] testsuite: make tests known to fail effectively fail Luc Van Oostenryck
2016-11-17 14:16   ` Christopher Li
2016-11-02 21:45 ` Luc Van Oostenryck [this message]
2016-11-17 16:13   ` [PATCH 3/5] testsuite: report as error tests known to fail but which succeed Christopher Li
2016-11-18 12:52     ` Luc Van Oostenryck
2016-11-19  0:44     ` Luc Van Oostenryck
2016-11-20  1:43       ` Christopher Li
2016-11-02 21:45 ` [PATCH 4/5] testsuite: simplify the ioc-typecheck case Luc Van Oostenryck
2016-11-17 16:17   ` Christopher Li
2016-11-02 21:45 ` [PATCH 5/5] testsuite: add a simple test for -Wenum-mismatch Luc Van Oostenryck
2016-11-17 16:25   ` 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=20161102214509.36571-4-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).