DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	 Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	 Nipun Gupta <nipun.gupta@nxp.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: dev <dev@dpdk.org>,
	Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>,
	Aaron Conole <aconole@redhat.com>, nd <nd@arm.com>,
	 Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: Re: [dpdk-dev] [PATCH] eal: change the log level for test assert macro
Date: Thu, 16 Jul 2020 17:06:58 +0200	[thread overview]
Message-ID: <CAJFAV8yDHPizra4xnUWH8uT3QF9tAXpnVe9NETSQCnmHc7zkGw@mail.gmail.com> (raw)
In-Reply-To: <20200715202006.19781-1-honnappa.nagarahalli@arm.com>

On Wed, Jul 15, 2020 at 10:20 PM Honnappa Nagarahalli
<honnappa.nagarahalli@arm.com> wrote:
>
> Change the log level for RTE_TEST_ASSERT macro to error to help
> log errors while running test cases.
>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> ---
>  lib/librte_eal/include/rte_test.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_eal/include/rte_test.h b/lib/librte_eal/include/rte_test.h
> index 89e47f47a..62c8f165a 100644
> --- a/lib/librte_eal/include/rte_test.h
> +++ b/lib/librte_eal/include/rte_test.h
> @@ -18,7 +18,7 @@
>
>  #define RTE_TEST_ASSERT(cond, msg, ...) do {                                  \
>         if (!(cond)) {                                                        \
> -               RTE_LOG(DEBUG, EAL, "Test assert %s line %d failed: "         \
> +               RTE_LOG(ERR, EAL, "Test assert %s line %d failed: "           \
>                                 msg "\n", __func__, __LINE__, ##__VA_ARGS__); \
>                 RTE_TEST_TRACE_FAILURE(__FILE__, __LINE__, __func__);         \
>                 return -1;                                                    \
> --
> 2.17.1
>

I proposed it, so I can't disagree :-)

RTE_TEST_ASSERT* are used in eventdev driver selftests.
I don't see why more output in error cases would be detrimental.
Any objection?

Thanks.

-- 
David Marchand


  parent reply	other threads:[~2020-07-16 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200715202024eucas1p2d1ddce75f7e5b1181d7a8f29b50fc4b5@eucas1p2.samsung.com>
2020-07-15 20:20 ` Honnappa Nagarahalli
2020-07-16 13:00   ` Aaron Conole
2020-07-16 18:40     ` Honnappa Nagarahalli
2020-07-16 15:06   ` David Marchand [this message]
2020-07-16 18:41     ` Honnappa Nagarahalli
2020-07-16 15:16   ` Lukasz Wojciechowski
2020-07-16 18:39   ` [dpdk-dev] [PATCH v2] " Honnappa Nagarahalli
2020-07-17  8:54     ` David Marchand

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=CAJFAV8yDHPizra4xnUWH8uT3QF9tAXpnVe9NETSQCnmHc7zkGw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=l.wojciechow@partner.samsung.com \
    --cc=nd@arm.com \
    --cc=nipun.gupta@nxp.com \
    --cc=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    /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).