From: "Li, WenjieX A" <wenjiex.a.li@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1] tests/fdir: ensure port is up before send packets
Date: Fri, 18 Oct 2019 08:10:21 +0000 [thread overview]
Message-ID: <8688172CD5C0B74590FAE19D9579F94B537BF2F1@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1571418047-13283-1-git-send-email-wenjiex.a.li@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
Tested-by: Li, WenjieX A <wenjiex.a.li@intel.com>
> -----Original Message-----
> From: Li, WenjieX A
> Sent: Saturday, October 19, 2019 1:01 AM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts][PATCH V1] tests/fdir: ensure port is up before send packets
>
> ensure the port is up before send packets; if the port is down, wait for at most
> 15s, then return failure with 'link is down'.
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> tests/TestSuite_fdir.py | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/TestSuite_fdir.py b/tests/TestSuite_fdir.py index
> 9f5a812..d74a06e 100644
> --- a/tests/TestSuite_fdir.py
> +++ b/tests/TestSuite_fdir.py
> @@ -87,6 +87,11 @@ class TestFdir(TestCase, IxiaPacketGenerator):
> """
> self.scapyCmds.append(packet)
> self.dut.send_expect("start", "testpmd>")
> +
> + self.pmd_output = PmdOutput(self.dut)
> + res = self.pmd_output.wait_link_status_up('all', timeout=15)
> + self.verify(res is True, 'there have port link is down')
> +
> self.scapy_execute()
> time.sleep(.5)
> out = self.dut.get_session_output()
> --
> 2.17.1
[-- Attachment #2: TestFdir.log --]
[-- Type: application/octet-stream, Size: 944573 bytes --]
next prev parent reply other threads:[~2019-10-18 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 17:00 Wenjie Li
2019-10-18 8:10 ` Li, WenjieX A [this message]
2019-10-23 9:51 ` Tu, Lijuan
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=8688172CD5C0B74590FAE19D9579F94B537BF2F1@SHSMSX103.ccr.corp.intel.com \
--to=wenjiex.a.li@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).