From: "Mo, YufengX" <yufengx.mo@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>,
"Peng, ZhihongX" <zhihongx.peng@intel.com>,
"Li, WenjieX A" <wenjiex.a.li@intel.com>,
"Zhang, YanX A" <yanx.a.zhang@intel.com>
Cc: "Yu, PingX" <pingx.yu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/TestSuite_ipgre.py: Tear_down func increase kill testpmd statement. check_packet_transmission func exiting abnormally willcause testpmd to not exit. The next test case continues to use untested testpmd, causing the test case to
Date: Mon, 16 Sep 2019 08:31:40 +0000 [thread overview]
Message-ID: <B8B15C44A3F2C044966E545C7B7371153E849407@shsmsx102.ccr.corp.intel.com> (raw)
Hi, peng zhihong
Li,wenjie has one patch to do the same thing. Could you sync with him?
[dts] [PATCH V1] tests/ipgre: optimize script
BRs
Yufen, Mo
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Zhihong
> Sent: Monday, September 16, 2019 10:10 PM
> To: dts@dpdk.org
> Cc: Peng, ZhihongX <zhihongx.peng@intel.com>; Peng@dpdk.org
> Subject: [dts] [PATCH V1] tests/TestSuite_ipgre.py: Tear_down func increase kill testpmd statement. check_packet_transmission func
> exiting abnormally willcause testpmd to not exit. The next test case continues to use untested testpmd, causing the test case to f...
>
> From: "Peng, ZhihongX" <zhihongx.peng@intel.com>
>
> Signed-off-by: Peng, ZhihongX <zhihongx.peng@intel.com>
> ---
> tests/TestSuite_ipgre.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/TestSuite_ipgre.py b/tests/TestSuite_ipgre.py
> index d74ac05..d1db8df 100644
> --- a/tests/TestSuite_ipgre.py
> +++ b/tests/TestSuite_ipgre.py
> @@ -439,6 +439,7 @@ class TestIpgre(TestCase):
> Run after each test case.
> Nothing to do.
> """
> + self.dut.kill_all()
> pass
>
> def tear_down_all(self):
> --
> 2.17.1
next reply other threads:[~2019-09-16 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 8:31 Mo, YufengX [this message]
2019-09-16 8:35 ` Li, WenjieX A
2019-09-20 6:24 Tu, Lijuan
2019-09-23 1:49 ` Peng, ZhihongX
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=B8B15C44A3F2C044966E545C7B7371153E849407@shsmsx102.ccr.corp.intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=pingx.yu@intel.com \
--cc=wenjiex.a.li@intel.com \
--cc=yanx.a.zhang@intel.com \
--cc=zhihongx.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).