test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Wang, Yinan" <yinan.wang@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V4]tests/packet_capture: upload automation script
Date: Tue, 30 Jul 2019 12:17:26 +0000	[thread overview]
Message-ID: <E0CBA5A1980F1F408E1F28F9991B5B1D50EDEC74@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1564466015-44060-1-git-send-email-yufengx.mo@intel.com>

Acked-by: Wang, Yinan <yinan.wang@intel.com>

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: 2019年7月30日 13:54
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V4]tests/packet_capture: upload automation script
> 
>  upload packet capture automation script
> 
> v4:
>  -  *. copy old tcpdump sniff/load methods of packet module into suite script to
> make sure testing time consumption < 45 minutes.
>  -  *. fix timeout error when run on dut/tester two nodes scenario.
>  -  *. add exception process to make sure testpmd and pdump can quit
> normally when exception occurs.
>  -  *. add check condition before run remote copy.
>  -  *. remove debug source code.
>  -  *. fix typo issue.
>  -  *. fix pep8 issue.
> 
> yufengmx (1):
>   tests/packet_capture: upload automation script
> 
>  tests/TestSuite_packet_capture.py | 869
> ++++++++++++++++++++++++++++++++++++++
>  1 file changed, 869 insertions(+)
>  create mode 100644 tests/TestSuite_packet_capture.py
> 
> --
> 1.9.3


      parent reply	other threads:[~2019-07-30 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30  5:53 yufengmx
2019-07-30  5:53 ` yufengmx
2019-07-30 12:18   ` Wang, Yinan
2019-08-08  5:48   ` Tu, Lijuan
2019-07-30 12:17 ` Wang, Yinan [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=E0CBA5A1980F1F408E1F28F9991B5B1D50EDEC74@SHSMSX104.ccr.corp.intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.org \
    --cc=yufengx.mo@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).