DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "jspewock@iol.unh.edu" <jspewock@iol.unh.edu>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
	"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
	"ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
	"stable@dpdk.org" <stable@dpdk.org>, nd <nd@arm.com>
Subject: RE: [PATCH] test/ipsec: fix invalid crypto device failing
Date: Thu, 4 Aug 2022 08:27:05 +0000	[thread overview]
Message-ID: <AS8PR08MB70808C0D23D21A1BF96725609E9F9@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20220712141701.27797-1-jspewock@iol.unh.edu>

> -----Original Message-----
> From: jspewock@iol.unh.edu <jspewock@iol.unh.edu>
> Sent: Tuesday, July 12, 2022 10:17 PM
> To: dev@dpdk.org
> Cc: bernard.iremonger@intel.com; juraj.linkes@pantheon.tech;
> ohilyard@iol.unh.edu; Jeremy Spewock <jspewock@iol.unh.edu>;
> stable@dpdk.org
> Subject: [PATCH] test/ipsec: fix invalid crypto device failing
> 
> From: Jeremy Spewock <jspewock@iol.unh.edu>
> 
> ipsec_autotest is now skipped if no compatible crypto devices are found.
> 
> Fixes issue where if at least one crypto device was found but no
> compatible crypto devices for the ipsec_autotest test case are present
> the case would fail with no error message. Now, when this situation is
> encountered, the test case will be skipped with an explanation.
> 
> Fixes: 59d7353b0df0 ("test/ipsec: fix test suite setup")
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jeremy Spewock <jspewock@iol.unh.edu>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---
>  app/test/test_ipsec.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/app/test/test_ipsec.c b/app/test/test_ipsec.c index
> 7047e17960..7c03a06785 100644
> --- a/app/test/test_ipsec.c
> +++ b/app/test/test_ipsec.c
> @@ -320,8 +320,10 @@ testsuite_setup(void)
>  		}
>  	}
> 
> -	if (ts_params->valid_dev_found == 0)
> -		return TEST_FAILED;
> +	if (ts_params->valid_dev_found == 0) {
> +		RTE_LOG(WARNING, USER1, "No compatible crypto device
> found.\n");
> +		return TEST_SKIPPED;
> +	}
> 
>  	ts_params->mbuf_pool = rte_pktmbuf_pool_create(
>  			"CRYPTO_MBUFPOOL",
> --
> 2.35.1
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>



  reply	other threads:[~2022-08-04  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 14:17 jspewock
2022-08-04  8:27 ` Ruifeng Wang [this message]
2022-08-26 12:12   ` Akhil Goyal

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=AS8PR08MB70808C0D23D21A1BF96725609E9F9@AS8PR08MB7080.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=jspewock@iol.unh.edu \
    --cc=juraj.linkes@pantheon.tech \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).