test suite reviews and discussions
 help / color / mirror / Atom feed
From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, weix.xie@intel.com, yinan.wang@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V2 1/1] metrics: add prefix for new frame work.
Date: Wed,  4 Mar 2020 12:53:02 +0800	[thread overview]
Message-ID: <20200304045302.5029-2-yufengx.mo@intel.com> (raw)
In-Reply-To: <20200304045302.5029-1-yufengx.mo@intel.com>


add prefix for new frame work.

Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
 tests/TestSuite_metrics.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tests/TestSuite_metrics.py b/tests/TestSuite_metrics.py
index 148365c..3eb9f56 100644
--- a/tests/TestSuite_metrics.py
+++ b/tests/TestSuite_metrics.py
@@ -187,7 +187,7 @@ class TestMetrics(TestCase):
         self.is_pmd_on = False
 
     def init_proc_info_tool(self):
-        option = ' -v -- --metrics'
+        option = f' -v {self.prefix} -- --metrics'
         self.dpdk_proc = os.path.join(
             self.target_dir, self.target, "app", "dpdk-procinfo" + option)
         self.metrics_stat = []
@@ -785,6 +785,7 @@ class TestMetrics(TestCase):
     def set_up_all(self):
         self.dut_ports = self.dut.get_ports(self.nic)
         self.verify(len(self.dut_ports) >= 2, "Not enough ports")
+        self.prefix = "dpdk_" + self.dut.prefix_subfix
         # prepare testing environment
         self.preset_test_environment()
 
-- 
2.21.0


  reply	other threads:[~2020-03-04  4:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  4:53 [dts] [PATCH V2 0/1] " yufengmx
2020-03-04  4:53 ` yufengmx [this message]
2020-03-04  8:22 ` Mo, YufengX

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=20200304045302.5029-2-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    --cc=weix.xie@intel.com \
    --cc=yinan.wang@intel.com \
    /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).