From: yaobing <bingx.y.yao@intel.com>
To: dts@dpdk.org
Cc: yaobing <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V1] tests/ipsec_gw:build ipsec-secgw before tests
Date: Mon, 10 Jun 2019 15:46:51 +0800 [thread overview]
Message-ID: <1560152811-152029-1-git-send-email-bingx.y.yao@intel.com> (raw)
build the sample app ipsec-secgw before tests
Signed-off-by: yaobing <bingx.y.yao@intel.com>
---
tests/TestSuite_ipsec_gw_cryptodev_func.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/TestSuite_ipsec_gw_cryptodev_func.py b/tests/TestSuite_ipsec_gw_cryptodev_func.py
index dc49577..f4e2f37 100644
--- a/tests/TestSuite_ipsec_gw_cryptodev_func.py
+++ b/tests/TestSuite_ipsec_gw_cryptodev_func.py
@@ -79,6 +79,9 @@ class TestIPsecGW(TestCase):
self._app_path = "./examples/ipsec-secgw/build/ipsec-secgw"
if not cc.is_build_skip(self):
cc.build_dpdk_with_cryptodev(self)
+ out =self.dut.build_dpdk_apps("./examples/ipsec-secgw")
+ self.verify("Error"not in out,"Compilation error")
+ self.verify("No such"not in out,"Compilation error")
self.vf_driver = self.get_suite_cfg()['vf_driver']
cc.bind_qat_device(self, self.vf_driver)
--
2.17.2
next reply other threads:[~2019-06-10 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 7:46 yaobing [this message]
2019-06-10 7:45 ` Zhu, ShuaiX
2019-06-12 2:53 ` 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=1560152811-152029-1-git-send-email-bingx.y.yao@intel.com \
--to=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).