From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/5] more testsuite improvements
Date: Thu, 5 Jan 2017 06:16:27 +0100 [thread overview]
Message-ID: <20170105051632.8392-1-luc.vanoostenryck@gmail.com> (raw)
This serie is a continuation of a similar previous sent in
November. It has three parts:
- patch 1: give a bit more flexibility when testing the test output,
from test-linearize for example.
- patch 2: somehow correct a message from the testsuite
- patch 3-5: make the testsuite quieter regarding the 'known-to-fail'
tests.
This serie can also be found as:
git://github.com/lucvoo/sparse.git sent/testsuite2
Luc Van Oostenryck (5):
testsuite: check the nbr of times a pattern should be present
testsuite: use 'error' instead of 'info' for successful tests known to fail
testsuite: get 'check-known-to-fail' earlier
testsuite: allow quieter error reporting
testsuite: quieter error reporting for 'known-to-fail'
Documentation/test-suite | 4 ++++
validation/test-suite | 42 ++++++++++++++++++++++++++++++++++++------
2 files changed, 40 insertions(+), 6 deletions(-)
next reply other threads:[~2017-01-05 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 5:16 Luc Van Oostenryck [this message]
2017-01-05 5:16 ` [PATCH 1/5] testsuite: check the nbr of times a pattern should be present Luc Van Oostenryck
2017-01-05 5:16 ` [PATCH 2/5] testsuite: use 'error' instead of 'info' for successful tests known to fail Luc Van Oostenryck
2017-01-05 5:16 ` [PATCH 3/5] testsuite: get 'check-known-to-fail' earlier Luc Van Oostenryck
2017-01-05 5:16 ` [PATCH 4/5] testsuite: allow quieter error reporting Luc Van Oostenryck
2017-01-05 5:16 ` [PATCH 5/5] testsuite: quieter error reporting for 'known-to-fail' Luc Van Oostenryck
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=20170105051632.8392-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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).