test suite reviews and discussions
 help / color / mirror / Atom feed
From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>, "peng,yuan" <yuan.peng@intel.com>
Subject: [dts] [PATCH V1] fix test suite unit_tests_lpm failed on freeBSD
Date: Mon, 16 Oct 2017 10:19:28 +0800	[thread overview]
Message-ID: <1508120368-10539-1-git-send-email-gangx.xu@intel.com> (raw)

freebsd have not path '/proc/meminfo'
Signed-off-by: peng,yuan <yuan.peng@intel.com>
---
 tests/TestSuite_unit_tests_lpm.py | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_unit_tests_lpm.py b/tests/TestSuite_unit_tests_lpm.py
index f9a2bf7..337e891 100644
--- a/tests/TestSuite_unit_tests_lpm.py
+++ b/tests/TestSuite_unit_tests_lpm.py
@@ -81,11 +81,13 @@ class TestUnitTestsLpmIpv6(TestCase):
         """
         [arch, machine, env, toolchain] = self.target.split('-')
         self.verify(arch in ["x86_64", "arm64"], "lpm6 request huge memory")
-        hugepages_size = int(self.dut.send_expect("awk '/Hugepagesize/ {print $2}' /proc/meminfo", "# "))
-	hugepage_ori = self.dut.get_total_huge_pages()
+
 	if env == 'bsdapp':
             pass
         else:
+            hugepages_size = int(self.dut.send_expect(
+                "awk '/Hugepagesize/ {print $2}' /proc/meminfo", "# "))
+            hugepage_ori = self.dut.get_total_huge_pages()
 	    hugepage_8G = 8 * 1024 * 1024
             total_hugepage = hugepages_size * hugepage_ori
             self.verify(total_hugepage >= hugepage_8G,"have no enough hugepage")
-- 
1.9.3

             reply	other threads:[~2017-10-16  2:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  2:19 xu,gang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-16  3:13 xu,gang
2017-09-11  3:07 xu,gang

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=1508120368-10539-1-git-send-email-gangx.xu@intel.com \
    --to=gangx.xu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yuan.peng@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).