From: Bruce Richardson <bruce.richardson@intel.com>
To: Ayuj Verma <ayverma@marvell.com>
Cc: akhil.goyal@nxp.com, fiona.trahe@intel.com,
arkadiuszx.kusztal@intel.com, pablo.de.lara.guarch@intel.com,
shallyv@marvell.com, ssahu@marvell.com, kkotamarthy@marvell.com,
adesai@marvell.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] app/test: replace TEST_SKIPPED with -ENOTSUP
Date: Tue, 9 Apr 2019 15:55:32 +0100 [thread overview]
Message-ID: <20190409145532.GA693@bricha3-MOBL.ger.corp.intel.com> (raw)
Message-ID: <20190409145532.TbNM_S8jgzAffJeRmnaFLPgAk_H_y6-63svzu5ancFs@z> (raw)
In-Reply-To: <1554809619-21164-2-git-send-email-ayverma@marvell.com>
On Tue, Apr 09, 2019 at 05:03:39PM +0530, Ayuj Verma wrote:
> Return -ENOTSUP for unsupported tests
>
I disagree with this, since TEST_SKIPPED is the correct return value for
unsupported test conditions IMHO. If part of the current infrastructure
doesn't support that return value, I think the infrastructure should be
updated.
Ref: http://mesonbuild.com/Unit-tests.html#skipped-tests-and-hard-errors
/Bruce
next prev parent reply other threads:[~2019-04-09 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 11:33 [dpdk-dev] [PATCH v2] fix return value for skipped tests Ayuj Verma
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 [this message]
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=20190409145532.GA693@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=adesai@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ayverma@marvell.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).