automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw101440-101451 [PATCH] [v7, 12/12] net/sfc: support port representor flow item
Date: Wed, 13 Oct 2021 17:44:41 +0000 (UTC)	[thread overview]
Message-ID: <20211013174441.62CDA6009A@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/101440

_apply patch failure_

Submitter: Ivan Malov <Ivan.Malov@oktetlabs.ru>
Date: Wednesday, October 13 2021 17:34:48 
Applied on: CommitID:2f3758751b157760ebb6fc51cd92841073bb115c
Apply patch set 101440-101451 failed:

Checking patch doc/guides/prog_guide/rte_flow.rst...
Hunk #5 succeeded at 1981 (offset 15 lines).
Hunk #6 succeeded at 2005 (offset 15 lines).
Hunk #7 succeeded at 2033 (offset 15 lines).
Hunk #8 succeeded at 2056 (offset 15 lines).
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
  to support modifying fields larger than 64 bits.
  In addition, documentation will be updated to clarify byte order.

* ethdev: Definition of the flow API action ``RTE_FLOW_ACTION_TYPE_PORT_ID``
  is ambiguous and needs clarification.
  Structure ``rte_flow_action_port_id`` will be extended to specify
  traffic direction to the represented entity or ethdev port itself
  in DPDK 21.11.

* ethdev: Flow API documentation is unclear if ethdev port used to create
  a flow rule adds any implicit match criteria in the case of transfer rules.
  The semantics will be clarified in DPDK 21.11 and it will require fixes in

error: patch failed: doc/guides/rel_notes/deprecation.rst:113
Hunk #2 succeeded at 158 (offset 15 lines).
Checking patch doc/guides/rel_notes/release_21_11.rst...
Hunk #1 succeeded at 228 (offset -26 lines).
Checking patch lib/ethdev/rte_flow.h...
Hunk #8 succeeded at 2018 (offset -8 lines).
Hunk #9 succeeded at 2030 (offset -8 lines).
Hunk #10 succeeded at 2042 (offset -8 lines).
Hunk #11 succeeded at 2054 (offset -8 lines).
Hunk #12 succeeded at 2698 (offset 6 lines).
Hunk #13 succeeded at 2720 (offset 6 lines).
Hunk #14 succeeded at 2738 (offset 6 lines).
Applied patch doc/guides/prog_guide/rte_flow.rst cleanly.
Applying patch doc/guides/rel_notes/deprecation.rst with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
Applied patch doc/guides/rel_notes/release_21_11.rst cleanly.
Applied patch lib/ethdev/rte_flow.h cleanly.
diff a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst	(rejected hunks)
@@ -113,12 +113,6 @@ Deprecation Notices
   to support modifying fields larger than 64 bits.
   In addition, documentation will be updated to clarify byte order.
 
-* ethdev: Definition of the flow API action ``RTE_FLOW_ACTION_TYPE_PORT_ID``
-  is ambiguous and needs clarification.
-  Structure ``rte_flow_action_port_id`` will be extended to specify
-  traffic direction to the represented entity or ethdev port itself
-  in DPDK 21.11.
-
 * ethdev: Flow API documentation is unclear if ethdev port used to create
   a flow rule adds any implicit match criteria in the case of transfer rules.
   The semantics will be clarified in DPDK 21.11 and it will require fixes in
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: doc/guides/prog_guide/rte_flow.rst: does not match index
Checking patch doc/guides/rel_notes/deprecation.rst...
error: doc/guides/rel_notes/deprecation.rst: does not match index
Checking patch doc/guides/rel_notes/release_21_11.rst...
error: doc/guides/rel_notes/release_21_11.rst: does not match index
Checking patch lib/ethdev/rte_flow.h...
error: lib/ethdev/rte_flow.h: does not match index
Checking patch doc/guides/nics/features/octeontx2.ini...
Checking patch doc/guides/nics/octeontx2.rst...
Checking patch drivers/net/octeontx2/otx2_flow_parse.c...
error: while searching for:
{
	struct otx2_eth_dev *hw = dev->data->dev_private;
	struct otx2_npc_flow_info *npc = &hw->npc_flow;
	const struct rte_flow_action_port_id *port_act;
	const struct rte_flow_action_mark *act_mark;
	const struct rte_flow_action_queue *act_q;
	const struct rte_flow_action_vf *vf_act;

error: patch failed: drivers/net/octeontx2/otx2_flow_parse.c:900
Hunk #2 succeeded at 987 (offset 11 lines).
Applied patch doc/guides/nics/features/octeontx2.ini cleanly.
Applied patch doc/guides/nics/octeontx2.rst cleanly.
Applying patch drivers/net/octeontx2/otx2_flow_parse.c with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
diff a/drivers/net/octeontx2/otx2_flow_parse.c b/drivers/net/octeontx2/otx2_flow_parse.c	(rejected hunks)
@@ -900,7 +900,6 @@ otx2_flow_parse_actions(struct rte_eth_dev *dev,
 {
 	struct otx2_eth_dev *hw = dev->data->dev_private;
 	struct otx2_npc_flow_info *npc = &hw->npc_flow;
-	const struct rte_flow_action_port_id *port_act;
 	const struct rte_flow_action_mark *act_mark;
 	const struct rte_flow_action_queue *act_q;
 	const struct rte_flow_action_vf *vf_act;

https://lab.dpdk.org/results/dashboard/patchsets/19385/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-10-13 17:44 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=20211013174441.62CDA6009A@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).