From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] testsuite: fix parsing of tags used in the testcases
Date: Fri, 11 Dec 2020 16:39:15 +0000 [thread overview]
Message-ID: <4176615c-73b8-ff5e-d705-f6a71ea49cab@ramsayjones.plus.com> (raw)
In-Reply-To: <20201211130619.71317-1-luc.vanoostenryck@gmail.com>
On 11/12/2020 13:06, Luc Van Oostenryck wrote:
> In testcases' tags, if a value contains 'check-' then this
> value will be used as the tagname instead of the value.
>
> Fix this by adding a bit more context in the regexp used for parsing these.
>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
> validation/test-suite | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/validation/test-suite b/validation/test-suite
> index 6935d40cee51..1b05c75e9f74 100755
> --- a/validation/test-suite
> +++ b/validation/test-suite
> @@ -84,8 +84,8 @@ get_tag_value()
> check_assert=""
> check_cpp_if=""
>
> - lines=$(grep 'check-[a-z-]*' $1 | \
> - sed -e 's/^.*\(check-[a-z-]*:*\) *\(.*\)$/\1 \2/')
> + lines=$(grep '^ \* check-[a-z-]*' $1 | \
> + sed -e 's/^ \* \(check-[a-z-]*:*\) *\(.*\)$/\1 \2/')
>
> while read tag val; do
> #echo "-> tag: '$tag'"
>
I needed to apply this to get the testsuite to pass on tonights
'fetch'. However, my immediate thought was 'what if you had more
than one space before/after the '*'?
It just so happens that I had a couple of 'warning: <file>: test unhandled'
after applying the patch (for asm-empty-clobber.c and asm-goto-labels.c)
where they had two spaces after the '*', so ... :-D
ATB,
Ramsay Jones
next prev parent reply other threads:[~2020-12-11 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 13:06 [PATCH] testsuite: fix parsing of tags used in the testcases Luc Van Oostenryck
2020-12-11 16:39 ` Ramsay Jones [this message]
2020-12-11 20:14 ` 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=4176615c-73b8-ff5e-d705-f6a71ea49cab@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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