From: "xu,huilong" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: [dts] [PATCH V1] define build_time in freebsd when compile dpdk
Date: Mon, 6 Mar 2017 10:13:18 +0800 [thread overview]
Message-ID: <1488766398-5314-1-git-send-email-huilongx.xu@intel.com> (raw)
Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
framework/project_dpdk.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/framework/project_dpdk.py b/framework/project_dpdk.py
index 7a4e4f7..3b91dd6 100644
--- a/framework/project_dpdk.py
+++ b/framework/project_dpdk.py
@@ -207,11 +207,11 @@ class DPDKdut(Dut):
self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
self.send_expect("rm -rf %s" % r'./app/test/test_resource_tar.res.o' , "#")
self.send_expect("rm -rf %s" % r'./app/test/test_pci_sysfs.res.o' , "#")
-
+ build_time = 120
# compile
out = self.send_expect("make -j %d install T=%s CC=gcc48" % (self.number_of_cores,
target),
- "#", 120)
+ "#", build_time)
#should not check test app compile status, because if test compile fail,
#all unit test can't exec, but others case will exec sucessfull
self.send_expect("make -j -C test/ CC=gcc48", "# ", build_time)
@@ -224,7 +224,7 @@ class DPDKdut(Dut):
self.logger.error("ERROR - try without '-j'")
# if Error try to execute make without -j option
out = self.send_expect("make install T=%s CC=gcc48" % target,
- "#", 120)
+ "#", build_time)
assert ("Error" not in out), "Compilation error..."
assert ("No rule to make" not in out), "No rule to make error..."
--
1.9.3
next reply other threads:[~2017-03-06 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 2:13 xu,huilong [this message]
2017-03-06 8:24 ` Liu, Yong
2017-03-06 8:29 ` Xu, HuilongX
2017-03-06 8:33 ` 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=1488766398-5314-1-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@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).