From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Breno Leitao <leitao@debian.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 2/3] selftests/powerpc: Create a new SKIP_IF macro
Date: Wed, 31 Oct 2018 12:44:04 -0300 [thread overview]
Message-ID: <871s86qfy3.fsf@morokweng.localdomain> (raw)
In-Reply-To: <1540996702-27161-2-git-send-email-leitao@debian.org>
Breno Leitao <leitao@debian.org> writes:
> This patch creates a new macro that skips a test and prints a message to
> stderr. This is useful to give an idea why the tests is being skipped,
> other than just skipping the test blindly.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Thiago Jung Bauermann <bauerman@linux.ibm.com>
> ---
> tools/testing/selftests/powerpc/include/utils.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/tools/testing/selftests/powerpc/include/utils.h b/tools/testing/selftests/powerpc/include/utils.h
> index da1b963cdb32..486c1782c23e 100644
> --- a/tools/testing/selftests/powerpc/include/utils.h
> +++ b/tools/testing/selftests/powerpc/include/utils.h
> @@ -72,6 +72,16 @@ do { \
> } \
> } while (0)
>
> +#define SKIP_IF_MSG(x, msg) \
> +do { \
> + if ((x)) { \
> + fprintf(stderr, \
> + "[SKIP] Test skipped on line %d: %s\n", \
> + __LINE__, msg); \
> + return MAGIC_SKIP_RETURN_VALUE; \
> + } \
> +} while (0)
> +
> #define _str(s) #s
> #define str(s) _str(s)
--
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2018-10-31 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 14:38 [PATCH v2 1/3] selftests/powerpc: Allocate base registers Breno Leitao
2018-10-31 14:38 ` [PATCH v2 2/3] selftests/powerpc: Create a new SKIP_IF macro Breno Leitao
2018-10-31 15:44 ` Thiago Jung Bauermann [this message]
2018-10-31 14:38 ` [PATCH v2 3/3] selftests/powerpc: Skip test instead of failing Breno Leitao
2018-10-31 15:45 ` Thiago Jung Bauermann
2018-11-27 9:22 ` [v2,1/3] selftests/powerpc: Allocate base registers Michael Ellerman
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=871s86qfy3.fsf@morokweng.localdomain \
--to=bauerman@linux.ibm.com \
--cc=leitao@debian.org \
--cc=linuxppc-dev@lists.ozlabs.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