test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Huang, ZhiminX" <zhiminx.huang@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Lin, Xueqin" <xueqin.lin@intel.com>,
	"Huang, ZhiminX" <zhiminx.huang@intel.com>
Subject: Re: [dts] [PATCH V2 4/4] tests/iavf_fdir:add esp flow test case
Date: Mon, 27 Sep 2021 05:20:59 +0000	[thread overview]
Message-ID: <3d9c2497c07e4e7aa4eccb912550645d@intel.com> (raw)
In-Reply-To: <20210914181204.20088-5-zhiminx.huang@intel.com>

> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Zhimin Huang
> Sent: 2021年9月15日 2:12
> To: dts@dpdk.org
> Cc: Lin, Xueqin <xueqin.lin@intel.com>; Huang, ZhiminX
> <zhiminx.huang@intel.com>
> Subject: [dts] [PATCH V2 4/4] tests/iavf_fdir:add esp flow test case
> 
> add 21.08 new feature testcase,this feature support esp flow to match outer ip
> header.
> take ip src/dst and spi for inputset,add 4 new cases in iavf_fdir test suite.
> 
> Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>

It didn't pass CI testing, please fix them and re-submit.

DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan

iavf_fdir_test_plan.rst:49: WARNING: Malformed table.

+------------------------------+------------------------------+-------------------------------------------------------------------+
|    Packet Type               |        Pattern               |            Input Set                                              |
--
+------------------------------+------------------------------+-------------------------------------------------------------------+
|                              |MAC_IPV4_GTPU_EH_UL_IPV6_TCP  | inner:[Source IPv6], [Dest IPv6], [Source Port], [Dest Port]      |
+------------------------------+------------------------------+-------------------------------------------------------------------+
iavf_fdir_test_plan.rst:3686: WARNING: Literal block expected; none found.
iavf_fdir_test_plan.rst:3899: WARNING: Literal block expected; none found.
rxtx_offload_test_plan.rst:741: WARNING: Unexpected indentation.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team

      parent reply	other threads:[~2021-09-27  5:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 18:12 [dts] [PATCH V2 0/4] enable esp flow Zhimin Huang
2021-09-14 18:12 ` [dts] [PATCH V2 1/4] test_plans/cvl_fdir_test_plan:add esp flow test plan Zhimin Huang
2021-09-15  3:27   ` Lin, Xueqin
2021-09-14 18:12 ` [dts] [PATCH V2 2/4] test_plans/iavf_fdir_test_plan:add " Zhimin Huang
2021-09-15  3:27   ` Lin, Xueqin
2021-09-14 18:12 ` [dts] [PATCH V2 3/4] tests/cvl_fdir:add esp flow test case Zhimin Huang
2021-09-15  3:28   ` Lin, Xueqin
2021-09-14 18:12 ` [dts] [PATCH V2 4/4] tests/iavf_fdir:add " Zhimin Huang
2021-09-15  3:28   ` Lin, Xueqin
2021-09-27  5:20   ` 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=3d9c2497c07e4e7aa4eccb912550645d@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=xueqin.lin@intel.com \
    --cc=zhiminx.huang@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).