From: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>,
"Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/virtio_perf:change the method of verify_result
Date: Fri, 14 Jun 2019 09:54:18 +0000 [thread overview]
Message-ID: <4DC48DF9BDA3E54A836D2D3C057DEC6F0B1A9724@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1560504466-4045-1-git-send-email-bingx.y.yao@intel.com>
Tested-by: Zhu, ShuaiX <shuaix.zhu@intel.com>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yaobing
> Sent: Friday, June 14, 2019 5:28 PM
> To: dts@dpdk.org
> Cc: Yao, BingX Y <bingx.y.yao@intel.com>
> Subject: [dts] [PATCH V1] tests/virtio_perf:change the method of verify_result
>
> change the method of verify_result
>
> Signed-off-by: yaobing <bingx.y.yao@intel.com>
> ---
> tests/TestSuite_virtio_perf_cryptodev_func.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/TestSuite_virtio_perf_cryptodev_func.py
> b/tests/TestSuite_virtio_perf_cryptodev_func.py
> index 1f23363..b0b23d5 100644
> --- a/tests/TestSuite_virtio_perf_cryptodev_func.py
> +++ b/tests/TestSuite_virtio_perf_cryptodev_func.py
> @@ -209,7 +209,7 @@ class VirtioCryptodevPerfTest(TestCase):
> crypto_perf_opt_str = cc.get_opt_str(self,
> self._default_crypto_perf_opts)
> out = self._run_crypto_perf(eal_opt_str, crypto_perf_opt_str)
> self.logger.info(out)
> - self.verify("Failed" not in out, "Test fail")
> + self.verify("Enqueued" in out, "Test fail")
> self.verify("Error" not in out, "Test fail")
>
> def test_virtio_aes_cbc_sha1_hmac(self):
> @@ -220,7 +220,7 @@ class VirtioCryptodevPerfTest(TestCase):
> crypto_perf_opt_str = cc.get_opt_str(self,
> self._default_crypto_perf_opts)
> out = self._run_crypto_perf(eal_opt_str, crypto_perf_opt_str)
> self.logger.info(out)
> - self.verify("Failed" not in out, "Test fail")
> + self.verify("Enqueued" in out, "Test fail")
> self.verify("Error" not in out, "Test fail")
>
> def _run_crypto_perf(self, eal_opt_str, crypto_perf_opt_str):
> --
> 2.17.2
next prev parent reply other threads:[~2019-06-14 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 9:27 yaobing
2019-06-14 9:54 ` Zhu, ShuaiX [this message]
2019-06-26 6:58 ` Tu, Lijuan
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=4DC48DF9BDA3E54A836D2D3C057DEC6F0B1A9724@SHSMSX101.ccr.corp.intel.com \
--to=shuaix.zhu@intel.com \
--cc=bingx.y.yao@intel.com \
--cc=dts@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).