From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(103208-103213) sid(20116) job(DTS_AUTO879) [V1, 6/6] test_plans/iavf_fdir: update test plan for dpdk code change
Date: 29 Oct 2021 02:07:57 -0700 [thread overview]
Message-ID: <311d4e$iv4man@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/103213
Subject: [V1,6/6] test_plans/iavf_fdir: update test plan for dpdk code change
_Testing issues_
Diff:
tests/TestSuite_cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp.py
test_plans/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst
tests/TestSuite_cvl_advanced_rss_vlan_esp_ah_l2tp_pfcp.py
test_plans/cvl_advanced_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst
tests/TestSuite_cvl_fdir.py
test_plans/cvl_fdir_test_plan.rst
tests/TestSuite_flow_classify_softnic.py
test_plans/flow_classify_softnic_test_plan.rst
test_plans/cvl_switch_filter_pppoe_test_plan.rst
test_plans/iavf_fdir_test_plan.rst
DPDK:
commit efb57dd5bbf0ffac645d09ed4d0dbad088b602f1
Author: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed Oct 27 15:37:14 2021 +0000
Comment: doc: clarify SRIOV activation with built-in VFIO
DTS:
commit d33846d43cb66eae8e24cec68042693d57bb0504
Author: Jiale Song <songx.jiale@intel.com>
Date: Thu Oct 28 18:59:06 2021 +0800
Comment: tests/link_status_interrupt: optimize the method of checking priv_flags
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:4398: WARNING: Literal block expected; none found.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team
next reply other threads:[~2021-10-29 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 9:07 sys_stv [this message]
2021-10-29 11:38 sys_stv
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='311d4e$iv4man@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).