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(104638-104640) sid(20724) job(DTS_AUTO972) [v3, 3/3] tests/rte_flow_common: change common interface
Date: 23 Nov 2021 19:40:33 -0800	[thread overview]
Message-ID: <311d4e$jc4vdm@fmsmga001-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/104640
Subject: [v3,3/3] tests/rte_flow_common: change 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 f640b1f2a1fd9826c70c679e7e27af735925ae72
	Author: Jiale Song <songx.jiale@intel.com>
	Date:   Fri Nov 12 16:03:03 2021 +0800
	Comment: tests/cvl_fdir: add mark id

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

                 reply	other threads:[~2021-11-24  3:40 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='311d4e$jc4vdm@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).