DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ayuj Verma <ayverma@marvell.com>
To: <akhil.goyal@nxp.com>, <fiona.trahe@intel.com>,
	<arkadiuszx.kusztal@intel.com>, <pablo.de.lara.guarch@intel.com>
Cc: <shallyv@marvell.com>, <ssahu@marvell.com>,
	<kkotamarthy@marvell.com>, <adesai@marvell.com>, <dev@dpdk.org>,
	Ayuj Verma <ayverma@marvell.com>
Subject: [dpdk-dev] [PATCH v2] fix return value for skipped tests
Date: Tue, 9 Apr 2019 17:03:38 +0530	[thread overview]
Message-ID: <1554809619-21164-1-git-send-email-ayverma@marvell.com> (raw)
Message-ID: <20190409113338.kqWIrwWZd4tZ8UXzG0Bfr4LU_xaGB_UXP-LMUITW2BQ@z> (raw)

Currently some tests return TEST_SKIPPED/-1 when tests or params
are not supported for particular PMD because of which tests adds to
FAILED test counter in place of Skipped/Unsupported counter.

Since unsupported test is not a failure case,
replace return value TEST_SKIPPED/-1 with -ENOTSUP

Changes in v2:
        - Replace TEST_SKIPPED/-1 with -ENOTSUP

Ayuj Verma (1):
  app/test: replace TEST_SKIPPED with -ENOTSUP

 app/test/test_cryptodev_asym.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-04-09 11:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 11:33 Ayuj Verma [this message]
2019-04-09 11:33 ` Ayuj Verma
2019-04-09 11:33 ` [dpdk-dev] [PATCH v2] app/test: replace TEST_SKIPPED with -ENOTSUP Ayuj Verma
2019-04-09 11:33   ` Ayuj Verma
2019-04-09 14:55   ` Bruce Richardson
2019-04-09 14:55     ` Bruce Richardson
2019-04-10 12:33     ` [dpdk-dev] [EXT] " Ayuj Verma
2019-04-10 12:33       ` Ayuj Verma
2019-04-10 12:48       ` Bruce Richardson
2019-04-10 12:48         ` Bruce Richardson
2019-04-09 15:17   ` [dpdk-dev] " Trahe, Fiona
2019-04-09 15:17     ` Trahe, Fiona
2019-04-12  7:08     ` Ayuj Verma
2019-04-12  7:08       ` Ayuj Verma
2019-04-12 10:25       ` Trahe, Fiona
2019-04-12 10:25         ` Trahe, Fiona

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=1554809619-21164-1-git-send-email-ayverma@marvell.com \
    --to=ayverma@marvell.com \
    --cc=adesai@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=kkotamarthy@marvell.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=shallyv@marvell.com \
    --cc=ssahu@marvell.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;
as well as URLs for NNTP newsgroup(s).