From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(103577-103582) sid(20246) job(DTS_AUTO895) [V2, 6/6] tests/cvl_switch_filter_pppoe: update case code for dpdk code change
Date: 03 Nov 2021 00:10:43 -0700 [thread overview]
Message-ID: <5975f8$dcr8t6@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/103582
Subject: [V2,6/6] tests/cvl_switch_filter_pppoe: update case code 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/iavf_fdir_test_plan.rst
test_plans/cvl_switch_filter_pppoe_test_plan.rst
DPDK:
commit f88b0b892204d071a46a629b00424a8d47055ba4
Author: David Marchand <david.marchand@redhat.com>
Date: Fri Oct 22 22:55:31 2021 +0200
Comment: devtools: forbid indent with tabs in Meson
DTS:
commit 5b1f1f829daad677af5b513b52e066b7d91e46ed
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Wed Nov 3 01:27:02 2021 +0800
Comment: version: 21.08.0
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
reply other threads:[~2021-11-03 7:10 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='5975f8$dcr8t6@orsmga006-auth.jf.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).