From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(105807) sid(21167) job(DTS_AUTO_377) [V2] test_plans: add test plan for cvl flow priority
Date: 14 Jan 2022 00:49:46 -0800 [thread overview]
Message-ID: <8ea9f5$jvmsr1@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/105807
Subject: [V2] test_plans: add test plan for cvl flow priority
_Testing issues_
Diff:
test_plans/index.rst
test_plans/cvl_flow_priority_test_plan.rst
DPDK:
commit 6f716880ee53ac1e50c9c75dc749886e3257bb8f
Author: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Mon Nov 1 13:35:32 2021 +0000
Comment: devtools: remove ugly workaround from get maintainer
DTS:
commit 05702fb75716bb66706e983446646ea583bb1222
Author: Jiale Song <songx.jiale@intel.com>
Date: Thu Jan 13 16:32:53 2022 +0000
Comment: test_plans/iavf_*: modify test plan to adapt meson build
DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan
cvl_flow_priority_test_plan.rst:157: WARNING: Malformed table.
+---------------------+-------------------------------+-------------------------------------------+
| Packet Types | Pattern | input set (non-pipeline mode) |
--
| | MAC_VLAN_PPPOE_IPCP_PAY | [Dest MAC], [VLAN], [seid], |
| | | [pppoe_proto_id] |
+---------------------+-------------------------------+-------------------------------------------+
cvl_flow_priority_test_plan.rst:155: WARNING: Error parsing content block for the "table" directive: exactly one table expected.
.. table::
DPDK STV team
reply other threads:[~2022-01-14 8:49 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$jvmsr1@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).