From: Lijuan Tu <lijuanx.a.tu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH]tests cmdline,unit eal: extend ICC compilation time
Date: Wed, 2 Dec 2015 16:20:49 +0800 [thread overview]
Message-ID: <1449044449-5603-1-git-send-email-lijuanx.a.tu@intel.com> (raw)
Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
---
tests/TestSuite_unit_tests_cmdline.py | 6 +++++-
tests/TestSuite_unit_tests_eal.py | 6 +++++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_unit_tests_cmdline.py b/tests/TestSuite_unit_tests_cmdline.py
index 3ece175..e3a29ee 100644
--- a/tests/TestSuite_unit_tests_cmdline.py
+++ b/tests/TestSuite_unit_tests_cmdline.py
@@ -56,7 +56,11 @@ class TestUnitTestsCmdline(TestCase):
"""
Run at the start of each test suite.
"""
- out = self.dut.build_dpdk_apps('./app/test/')
+ # icc compilation cost long long time.
+ if "icc" in self.target:
+ out = self.dut.send_expect("make -j -C ./app/test/", "# ", 300)
+ else:
+ out = self.dut.build_dpdk_apps('./app/test/')
self.verify('make: Leaving directory' in out, "Compilation failed")
def set_up(self):
diff --git a/tests/TestSuite_unit_tests_eal.py b/tests/TestSuite_unit_tests_eal.py
index 040b3b9..663e961 100644
--- a/tests/TestSuite_unit_tests_eal.py
+++ b/tests/TestSuite_unit_tests_eal.py
@@ -30,7 +30,11 @@ class TestUnitTestsEal(TestCase):
"""
Run at the start of each test suite.
"""
- out = self.dut.build_dpdk_apps('./app/test/')
+ # icc compilation cost long long time.
+ if "icc" in self.target:
+ out = self.dut.send_expect("make -j -C ./app/test/", "# ", 300)
+ else:
+ out = self.dut.build_dpdk_apps('./app/test/')
self.verify('make: Leaving directory' in out, "Compilation failed")
[arch, machine, self.env, toolchain] = self.target.split('-')
self.start_test_time = 60
--
1.9.1
next reply other threads:[~2015-12-02 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 8:20 Lijuan Tu [this message]
2015-12-04 0:54 ` [dts] [PATCH]tests cmdline, unit " Liu, Yong
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=1449044449-5603-1-git-send-email-lijuanx.a.tu@intel.com \
--to=lijuanx.a.tu@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).