automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(107022) sid(21522) job(DTS_AUTO_486) [V3] test_plans/cvl_switch_filter: add test plan for cvl qinq switch filter support l4
Date: 08 Feb 2022 03:23:05 -0800	[thread overview]
Message-ID: <8ea9f5$k6l5vp@fmsmga001-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2584 bytes --]

Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/107022
Subject: [V3] test_plans/cvl_switch_filter: add test plan for cvl qinq switch filter support l4

_Testing issues_

Diff:
	test_plans/cvl_switch_filter_test_plan.rst

DPDK:
	commit 0e4dc6af06228c8504a5538512cb31ed7bf6cc23
	Author: Zhihong Wang <wangzhihong.wzh@bytedance.com>
	Date:   Tue Dec 14 11:30:16 2021 +0800
	Comment: ring: fix overflow in memory size calculation

DTS:
	commit 01d33c36cd9f54db3a50ee2521354292c68b3fda
	Author: Hailin Xu <hailinx.xu@intel.com>
	Date:   Mon Jan 17 23:41:04 2022 +0800
	Comment: tests/cvl_flow_priority: add pf flow priority cases

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

cvl_switch_filter_test_plan.rst:4854: WARNING: Title level inconsistent:

Test Steps
~~~~~~~~~~
cvl_switch_filter_test_plan.rst:4881: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:4893: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:4922: WARNING: Title level inconsistent:

Test Steps
~~~~~~~~~~
cvl_switch_filter_test_plan.rst:4949: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:4961: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:4990: WARNING: Title level inconsistent:

Test Steps
~~~~~~~~~~
cvl_switch_filter_test_plan.rst:5017: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5020: WARNING: Literal block ends without a blank line; unexpected unindent.
cvl_switch_filter_test_plan.rst:5028: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5057: WARNING: Title level inconsistent:

Test Steps
~~~~~~~~~~
cvl_switch_filter_test_plan.rst:5084: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5096: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5127: WARNING: Title level inconsistent:

Test Steps
~~~~~~~~~~
cvl_switch_filter_test_plan.rst:5154: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5160: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5189: WARNING: Title level inconsistent:

Test Steps
~~~~~~~~~~
cvl_switch_filter_test_plan.rst:5216: WARNING: Literal block expected; none found.
cvl_switch_filter_test_plan.rst:5228: WARNING: Literal block expected; none found.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team

                 reply	other threads:[~2022-02-08 11:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='8ea9f5$k6l5vp@fmsmga001-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=test-report@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).