automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw37358[dpdk-dev, v3, 2/4] ethdev: Add tunnel encap/decap actions
Date: 05 Jul 2018 01:37:01 -0700	[thread overview]
Message-ID: <0590c7$22vgch@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37358

_apply issues_

Submitter: Declan Doherty <declan.doherty@intel.com>
Date: 2018-04-06 12:24:01
DPDK git baseline:
	Repo:dpdk-master, CommitID: 05e0eee0001cb19671eb7e8d3dd68680a695fea2
	Repo:dpdk-next-eventdev, CommitID: aa9cbfc8cd1cae3e91e4741edc2aaf3d08056a39
	Repo:dpdk-next-net, CommitID: 0b8b92e38cd55c68e4dc49dd597f62327798ec74
	Repo:dpdk-next-crypto, CommitID: a5203e08a5e9b6ee9ffbbf4c150b7776de833b08
	Repo:dpdk-next-virtio, CommitID: 9b954f9c455a76304601deb88e2df1549dc9e09a

*Repo: dpdk-master
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Each possible action is represented by a type. Some have associated
configuration structures. Several actions combined in a list can be assigned
to a flow rule. That list is not ordered.

They fall in three categories:

- Terminating actions (such as QUEUE, DROP, RSS, PF, VF) that prevent
  processing matched packets by subsequent flow rules, unless overridden

error: patch failed: doc/guides/prog_guide/rte_flow.rst:997
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Each possible action is represented by a type. Some have associated
configuration structures. Several actions combined in a list can be assigned
to a flow rule. That list is not ordered.

They fall in three categories:

- Terminating actions (such as QUEUE, DROP, RSS, PF, VF) that prevent
  processing matched packets by subsequent flow rules, unless overridden

error: patch failed: doc/guides/prog_guide/rte_flow.rst:997
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-net
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Each possible action is represented by a type. Some have associated
configuration structures. Several actions combined in a list can be assigned
to a flow rule. That list is not ordered.

They fall in three categories:

- Terminating actions (such as QUEUE, DROP, RSS, PF, VF) that prevent
  processing matched packets by subsequent flow rules, unless overridden

error: patch failed: doc/guides/prog_guide/rte_flow.rst:997
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-crypto
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Each possible action is represented by a type. Some have associated
configuration structures. Several actions combined in a list can be assigned
to a flow rule. That list is not ordered.

They fall in three categories:

- Terminating actions (such as QUEUE, DROP, RSS, PF, VF) that prevent
  processing matched packets by subsequent flow rules, unless overridden

error: patch failed: doc/guides/prog_guide/rte_flow.rst:997
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-virtio
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Each possible action is represented by a type. Some have associated
configuration structures. Several actions combined in a list can be assigned
to a flow rule. That list is not ordered.

They fall in three categories:

- Terminating actions (such as QUEUE, DROP, RSS, PF, VF) that prevent
  processing matched packets by subsequent flow rules, unless overridden

error: patch failed: doc/guides/prog_guide/rte_flow.rst:997
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory

DPDK STV team

                 reply	other threads:[~2018-07-05  8:37 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='0590c7$22vgch@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --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).