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: [dpdk-test-report] [dts-test-report] |FAILURE| pw(100907-100908) sid(19480) job(DTS_AUTO755) [V1, 2/2] tests/cvl_switch_filter_pppoe: delete the placeholder fdir rule
Date: 11 Oct 2021 09:43:47 -0700	[thread overview]
Message-ID: <311d4e$ikjbf0@fmsmga001-auth.fm.intel.com> (raw)

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

Test-Label: Intel-doc-dts-test
Test-Status: SUCCESS
http://dpdk.org/patch/100908
Subject: [V1,2/2] tests/cvl_switch_filter_pppoe: delete the placeholder fdir rule

_Testing OK_

Diff:
	tests/TestSuite_cvl_switch_filter_pppoe.py
	test_plans/cvl_switch_filter_test_plan.rst
	test_plans/cvl_switch_filter_pppoe_test_plan.rst
	tests/TestSuite_cvl_switch_filter.py

DPDK:
	commit 515d20195b17444262a5732831c0615146c7189c
	Author: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
	Date:   Fri Oct 8 01:07:50 2021 +0300
	Comment: doc: remove unneeded min/max fields deprecations

DTS:
	commit b082e251348d7c20e09243a742136e6d93626fab
	Author: Thinh Tran <thinhtr@linux.vnet.ibm.com>
	Date:   Thu Sep 30 17:20:51 2021 +0000
	Comment: Framework:fix the first numa node may not be '0'

DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan

generic_flow_api_test_plan.rst:2090: WARNING: Literal block 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-10-11 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 16:43 sys_stv [this message]
2021-10-11 23:17 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$ikjbf0@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).