From: changqingxwu <changqingx.wu@intel.com>
To: dts@dpdk.org
Cc: changqingxwu <changqingx.wu@intel.com>
Subject: [dts] [PATCH V1] test_plans:add test plans about example build
Date: Mon, 28 Jan 2019 14:02:06 +0800 [thread overview]
Message-ID: <1548655326-39434-1-git-send-email-changqingx.wu@intel.com> (raw)
Signed-off-by: changqingxwu <changqingx.wu@intel.com>
---
test_plans/example_build_test_plan.rst | 71 ++++++++++++++++++++++++++
1 file changed, 71 insertions(+)
create mode 100644 test_plans/example_build_test_plan.rst
diff --git a/test_plans/example_build_test_plan.rst b/test_plans/example_build_test_plan.rst
new file mode 100644
index 0000000..22d793c
--- /dev/null
+++ b/test_plans/example_build_test_plan.rst
@@ -0,0 +1,71 @@
+.. Copyright (c) <2011>, Intel Corporation
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ - Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ - Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ - Neither the name of Intel Corporation nor the names of its
+ contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+ FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+
+=============
+Example Build
+=============
+
+This test case is for testing that all applications under DPDK examples compile successfully.
+Such as these applications::
+
+ - bbdev_app
+ - bond
+ - cmdline
+ - distributor
+ ...
+
+Prerequisites
+=============
+
+Dependency package requirements:
+
+ - libvert: https://libvirt.org/
+ - intel-cmt-cat: https://github.com/01org/intel-cmt-cat
+
+Test case: example build
+========================
+
+compile the applications of examples successfully::
+
+ make -j 70 -C examples
+
+If the compilation is successful, it will be the same as the shown in the terminal. ::
+
+ ...
+ LD load_balancer
+ INSTALL-APP l3fwd-thread
+ INSTALL-MAP l3fwd-thread.map
+ INSTALL-APP ipsec-secgw
+ INSTALL-MAP ipsec-secgw.map
+ INSTALL-MAP load_balancer.map
+ INSTALL-APP load_balancer
+ make: Leaving directory '/root/dpdk/examples'
--
2.17.2
next reply other threads:[~2019-01-28 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 6:02 changqingxwu [this message]
2019-01-28 6:54 ` Zhu, ShuaiX
2019-01-29 9:28 ` 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=1548655326-39434-1-git-send-email-changqingx.wu@intel.com \
--to=changqingx.wu@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).