test suite reviews and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: dts@dpdk.org
Cc: rdarawsheh@asaltech.com
Subject: [dts] [PATCH] fix queue start/stop case failed
Date: Tue, 27 Oct 2015 08:07:56 +0200	[thread overview]
Message-ID: <1445926076-31279-7-git-send-email-rasland@mellanox.com> (raw)
In-Reply-To: <1445926076-31279-1-git-send-email-rasland@mellanox.com>

From: "xu,huilong" <huilongx.xu@intel.com>

sometime print can't get  received package info, used self.dut.get_session_output() replace
 self.dut.send_expect("\n", "testpmd>") get received package info

Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
 tests/TestSuite_queue_start_stop.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/TestSuite_queue_start_stop.py b/tests/TestSuite_queue_start_stop.py
index 83504ab..f59333c 100644
--- a/tests/TestSuite_queue_start_stop.py
+++ b/tests/TestSuite_queue_start_stop.py
@@ -164,7 +164,7 @@ class TestQueueStartStop(TestCase):
             self.dut.send_expect("port 1 txq 0 stop", "testpmd>")
             self.dut.send_expect("start", "testpmd>")
             self.check_forwarding([0, 1], self.nic, received=False)
-            out = self.dut.send_expect("\n", "testpmd>")
+            out = self.dut.get_session_output()
         except Exception, e:
             raise IOError("queue start/stop forward failure: %s" % e)
 
-- 
1.9.1

  parent reply	other threads:[~2015-10-27  6:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27  6:07 [dts] [PATCH 1/6] framework: crb :add some parameters and check_Mellanox_pci function to identify mellanox device Raslan Darawsheh
2015-10-27  6:07 ` [dts] [PATCH 2/6] framework:dut : excluding mellanox NICs from beeing binded Raslan Darawsheh
2015-10-27  6:07 ` [dts] [PATCH 3/6] framework:settings :adding new defines for ConnectX_3_Pro and ConnectX_4 and there drivers Raslan Darawsheh
2015-10-27  6:07 ` [dts] [PATCH 4/6] framewark:project_dpdk : Enable MLX4 and MLX5 PMD's before compiling and disable binding Raslan Darawsheh
2015-10-27  6:07 ` [dts] [PATCH 5/6] framework:net_device : adding function get_interface_name_Mellanox to get the ConnectX_3_Pro interfaces Raslan Darawsheh
2015-10-27  6:07 ` [dts] [PATCH 6/6] framework:tester: adding ConnectX_3_Pro second port to the list of ports Raslan Darawsheh
2015-10-27  6:07 ` Raslan Darawsheh [this message]
2015-10-29  2:00 ` [dts] [PATCH 1/6] framework: crb :add some parameters and check_Mellanox_pci function to identify mellanox device Xu, HuilongX
2015-10-29  8:04   ` Raslan Darawsheh
2015-10-29  8:48     ` Xu, HuilongX
2015-10-29  9:58       ` Raslan Darawsheh
2015-10-29 10:10         ` Xu, HuilongX
2015-11-10  6:32           ` Raslan Darawsheh
2015-11-10  8:12             ` Liu, Yong
2016-01-18 11:18             ` Raslan Darawsheh
2016-01-19  6:05               ` Liu, Yong
2016-01-19  9:26                 ` Raslan Darawsheh
2016-01-20  9:24                   ` Liu, Yong
  -- strict thread matches above, loose matches on Subject: below --
2015-10-23  7:55 [dts] [PATCH] fix queue start/stop case failed xu,huilong
2015-10-23  8:06 ` 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=1445926076-31279-7-git-send-email-rasland@mellanox.com \
    --to=rasland@mellanox.com \
    --cc=dts@dpdk.org \
    --cc=rdarawsheh@asaltech.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).