From: Reshma Pattan <reshma.pattan@intel.com>
To: dts@dpdk.org
Cc: Reshma Pattan <reshma.pattan@intel.com>,
BoX.C.Chen@intel.com, ZbigniewX.Sikora@intel.com
Subject: [dts] [PATCH] framework: enhance regex for DPDK apps build
Date: Thu, 15 Apr 2021 13:04:24 +0100 [thread overview]
Message-ID: <20210415120424.17800-1-reshma.pattan@intel.com> (raw)
The below patch added regex enhancements to match latest DPDK build
output which contains '#'. But the patch missed to make same change
at another place.
https://git.dpdk.org/tools/dts/commit/?id=18c537316341ed2ec440b659835f40143ceba8b7
So, this patch extended the same fix to another place in "build_dpdk_apps" method.
CC: BoX.C.Chen@intel.com
CC: ZbigniewX.Sikora@intel.com
Signed-off-by: Sikora ZbigniewX <ZbigniewX.Sikora@intel.com>
Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
---
framework/project_dpdk.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/framework/project_dpdk.py b/framework/project_dpdk.py
index 0edb38a6..95efad64 100644
--- a/framework/project_dpdk.py
+++ b/framework/project_dpdk.py
@@ -576,9 +576,9 @@ class DPDKdut(Dut):
example = 'all'
else:
example = '/'.join(folder_info[folder_info.index('examples')+1:])
- out = self.send_expect("meson configure -Dexamples=%s %s" % (example, self.target), "# ")
+ out = self.send_expect("meson configure -Dexamples=%s %s" % (example, self.target), "[~|~\]]# ")
assert ("FAILED" not in out), "Compilation error..."
- out = self.send_expect("ninja -C %s" % self.target, "# ", timeout)
+ out = self.send_expect("ninja -C %s" % self.target, "[~|~\]]# ", timeout)
assert ("FAILED" not in out), "Compilation error..."
# verify the app build in the config path
--
2.17.1
next reply other threads:[~2021-04-15 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 12:04 Reshma Pattan [this message]
2021-04-16 1:48 ` Chen, BoX C
2021-04-20 11:54 ` Pattan, Reshma
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=20210415120424.17800-1-reshma.pattan@intel.com \
--to=reshma.pattan@intel.com \
--cc=BoX.C.Chen@intel.com \
--cc=ZbigniewX.Sikora@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).