From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Thinh Tran <thinhtr@linux.vnet.ibm.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "drc@linux.vnet.ibm.com" <drc@linux.vnet.ibm.com>
Subject: Re: [dts] [PATCH] test/shot_live: fix expecting string
Date: Fri, 13 Mar 2020 06:29:39 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBEC6EE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200304152426.294-1-thinhtr@linux.vnet.ibm.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Thinh Tran
> Sent: Wednesday, March 4, 2020 11:24 PM
> To: dts@dpdk.org
> Cc: drc@linux.vnet.ibm.com; Thinh Tran <thinhtr@linux.vnet.ibm.com>
> Subject: [dts] [PATCH] test/shot_live: fix expecting string
>
> - Not sure the "link state change event" is specific string for others,
> in general the testpmd does not produce it, but returns its prompt.
> This causes testcase Failed - TIMEOUT
> - change it back to expecting testpmd prompt
>
> Signed-off-by: Thinh Tran <thinhtr@linux.vnet.ibm.com>
> ---
> tests/TestSuite_short_live.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_short_live.py b/tests/TestSuite_short_live.py
> index 31adf0d..3e088ce 100644
> --- a/tests/TestSuite_short_live.py
> +++ b/tests/TestSuite_short_live.py
> @@ -168,7 +168,7 @@ class TestShortLiveApp(TestCase):
> for i in range(repeat_time):
> #dpdk start
> print("clean_up_with_signal_testpmd round %d" % (i + 1))
> - self.dut.send_expect("./%s/app/testpmd -c 0xf -n 4 -- -i --
> portmask=0x3" % self.target, "link state change event", 120)
> + self.dut.send_expect("./%s/app/testpmd -c 0xf -n 4 -- -i
> + --portmask=0x3" % self.target, "testpmd>", 120)
> self.dut.send_expect("set fwd mac", "testpmd>")
> self.dut.send_expect("set promisc all off", "testpmd>")
> self.dut.send_expect("start", "testpmd>")
> --
> 2.17.1
prev parent reply other threads:[~2020-03-13 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 15:24 Thinh Tran
2020-03-13 6:29 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BBEC6EE@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=drc@linux.vnet.ibm.com \
--cc=dts@dpdk.org \
--cc=thinhtr@linux.vnet.ibm.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).