From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(104585-104587) sid(20697) job(DTS_AUTO968) [v2, 3/3] tests/rte_flow_common: change rss common interface
Date: 22 Nov 2021 21:19:50 -0800 [thread overview]
Message-ID: <5975f8$djobdh@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/104587
Subject: [v2,3/3] tests/rte_flow_common: change rss common interface
_Testing issues_
Diff:
test_plans/cvl_rss_configure_test_plan.rst
tests/TestSuite_cvl_rss_configure.py
tests/rte_flow_common.py
DPDK:
commit 0c6e27549c03695f85d949f5195a166b449b419c
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Wed Nov 17 20:19:47 2021 +0100
Comment: version: 21.11-rc3
DTS:
commit f78b33713dcf275f9458ef3e0b60c1c60d0c1355
Author: DongJunX <junx.dong@intel.com>
Date: Wed Nov 17 17:26:30 2021 +0800
Comment: framework/test_case: removed bind_nic_driver common func to framework
DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan
cvl_rss_configure_test_plan.rst:473: WARNING: Enumerated list ends without a blank line; unexpected unindent.
cvl_rss_configure_test_plan.rst:541: WARNING: Enumerated list ends without a blank line; unexpected unindent.
cvl_rss_configure_test_plan.rst:609: WARNING: Enumerated list ends without a blank line; unexpected unindent.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team
next reply other threads:[~2021-11-23 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 5:19 sys_stv [this message]
2021-11-23 10:28 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='5975f8$djobdh@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).