All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 3/5] testsuite: report as error tests known to fail but which succeed
Date: Sat, 19 Nov 2016 01:44:12 +0100	[thread overview]
Message-ID: <20161119004411.GA20501@macpro.local> (raw)
In-Reply-To: <CANeU7QnHYuW7-h+wKFcQZe=6xNUZgNdSAtLnqdAm=OBNARvR-Q@mail.gmail.com>

On Fri, Nov 18, 2016 at 12:13:58AM +0800, Christopher Li wrote:
> On Thu, Nov 3, 2016 at 5:45 AM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> > 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.
> 
> I like what you are doing as a result.
> 
> But I think the implementation has room to improve.
> I don't like deep and messy "else" statement.
> 
> I attach a patch which I modify base on yours. I hope it is
> easier to read. Care to review it?
> 
> Chris

Like I said I prefer your version, but could you add the following patch
on top of yours?

---
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Date: Sat, 19 Nov 2016 01:28:31 +0100
Subject: [PATCH] testsuite: let the testsuite fail if we got any unexpected
 result

With this patch a failed test but known to fail will still be reported
as failed but won't make the whole testsuite to fail.
But a test known to fail but which succeed will make the testsuite
to fail. Normal tests, the ones not marked as known-to-fail, will
of course the testsuite to fail if one of them fail.

To put things simply: the testsuite will return a failure
if at least one test gave an unexpected result.

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

diff --git a/validation/test-suite b/validation/test-suite
index 4eff0150..ee6a90a5 100755
--- a/validation/test-suite
+++ b/validation/test-suite
@@ -11,6 +11,10 @@ if [ ! -x "$default_path/sparse-llvm" ]; then
 	disabled_cmds="sparsec sparsei sparse-llvm"
 fi
 
+# flags:
+#	- some tests gave an unexpected result
+failed=0
+
 # counts:
 #	- tests that have not been converted to test-suite format
 #	- tests that are disabled
@@ -165,6 +169,8 @@ do_test()
 	must_fail=`expr "$?" = 0`
 	known_ko_tests=`expr $known_ko_tests + $must_fail`
 
+	[ "$test_failed" -eq "$must_fail" ] || failed=1
+
 	if [ "$must_fail" -eq "1" ]; then
 		if [ "$test_failed" -eq "1" ]; then
 			echo "info: test '$file' is known to fail"
@@ -278,5 +284,5 @@ case "$1" in
 		;;
 esac
 
-exit 0
+exit $failed
 
-- 
2.10.2


  parent reply	other threads:[~2016-11-19  0:44 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 ` [PATCH 3/5] testsuite: report as error tests known to fail but which succeed Luc Van Oostenryck
2016-11-17 16:13   ` Christopher Li
2016-11-18 12:52     ` Luc Van Oostenryck
2016-11-19  0:44     ` Luc Van Oostenryck [this message]
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=20161119004411.GA20501@macpro.local \
    --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 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.