From: "Coyle, David" <david.coyle@intel.com>
To: "Troy, Rebecca" <rebecca.troy@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Power, Ciara" <ciara.power@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Akhil Goyal <gakhil@marvell.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/crypto: refactor DOCSIS to show hidden cases
Date: Tue, 2 Nov 2021 10:46:58 +0000 [thread overview]
Message-ID: <DM8PR11MB5575F5246A767E7B691E48D6E38B9@DM8PR11MB5575.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211029090418.151953-1-rebecca.troy@intel.com>
> -----Original Message-----
> From: Troy, Rebecca <rebecca.troy@intel.com>
> Sent: Friday, October 29, 2021 10:04 AM
> To: dev@dpdk.org
> Cc: Power, Ciara <ciara.power@intel.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>; Coyle, David <david.coyle@intel.com>; Troy,
> Rebecca <rebecca.troy@intel.com>; Akhil Goyal <gakhil@marvell.com>;
> Doherty, Declan <declan.doherty@intel.com>
> Subject: [PATCH v2] test/crypto: refactor DOCSIS to show hidden cases
>
> In the current implementation, the DOCSIS test cases are running and being
> reported as one test, despite the fact that multiple test cases are hidden
> inside i.e. "test_DOCSIS_PROTO_all" runs
> 52 test cases. Each DOCSIS test case should be reported individually instead.
>
> This commit achieves this by removing the use of the
> test_DOCSIS_PROTO_all function and statically listing the test cases to run
> when building the test suite, which are then reported to the user by
> description.
>
> Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
>
Looks good Rebecca
Reviewed-by: David Coyle <david.coyle@intel.com>
prev parent reply other threads:[~2021-11-02 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 10:53 [dpdk-dev] [PATCH] test/crypto: refactor docsis " Rebecca Troy
2021-10-28 10:34 ` Coyle, David
2021-10-28 10:41 ` Troy, Rebecca
2021-10-29 9:04 ` [dpdk-dev] [PATCH v2] test/crypto: refactor DOCSIS " Rebecca Troy
2021-11-02 10:40 ` Power, Ciara
2021-11-03 18:56 ` Akhil Goyal
2021-11-02 10:46 ` Coyle, David [this message]
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=DM8PR11MB5575F5246A767E7B691E48D6E38B9@DM8PR11MB5575.namprd11.prod.outlook.com \
--to=david.coyle@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=rebecca.troy@intel.com \
--cc=roy.fan.zhang@intel.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).