automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report]  |FAILURE| pw38732[dpdk-dev, v5, 4/4] ethdev: add shared counter support to rte_flow
Date: 24 Apr 2018 19:02:19 -0700	[thread overview]
Message-ID: <0590c7$1g6tfi@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Declan Doherty <declan.doherty@intel.com>
Date: 2018-04-23 15:56:20
DPDK git baseline:
	Repo:dpdk-master, CommitID: fa20485454178fd3a8912753a6a2ed6619dc64fb
	Repo:dpdk-next-eventdev, CommitID: fe5abd3150bc1caa8369e743c395c39f53265597
	Repo:dpdk-next-net, CommitID: 329502143e095229f8e90d5064849443c4250ef9
	Repo:dpdk-next-crypto, CommitID: eb8a86e275ef15a5455948d679d1a2c43dd4c740
	Repo:dpdk-next-virtio, CommitID: 81daf0ba4f2eb20c00975b474cb9b6ab71c44e25

*Repo: dpdk-master
Hunk #3 succeeded at 1381 (offset -63 lines).
Hunk #4 succeeded at 1396 (offset -63 lines).
Checking patch app/test-pmd/testpmd.h...
Hunk #1 succeeded at 603 (offset -13 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

.. table:: Mark, count then redirect

   +-------+--------+-----------+-------+
   | Index | Action | Field     | Value |
--
   +-------+----------------------------+

|


error: patch failed: doc/guides/prog_guide/rte_flow.rst:1153
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch drivers/net/failsafe/failsafe_flow.c...
Checking patch lib/librte_ether/rte_flow.c...
Hunk #1 succeeded at 201 (offset -2 lines).
Checking patch lib/librte_ether/rte_flow.h...
Hunk #1 succeeded at 957 (offset -78 lines).
*Repo: dpdk-next-eventdev
Hunk #3 succeeded at 1365 (offset -79 lines).
Hunk #4 succeeded at 1380 (offset -79 lines).
Checking patch app/test-pmd/testpmd.h...
Hunk #1 succeeded at 577 (offset -39 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

.. table:: Mark, count then redirect

   +-------+--------+-----------+-------+
   | Index | Action | Field     | Value |
--
   +-------+----------------------------+

|


error: patch failed: doc/guides/prog_guide/rte_flow.rst:1153
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch drivers/net/failsafe/failsafe_flow.c...
Checking patch lib/librte_ether/rte_flow.c...
Hunk #1 succeeded at 201 (offset -2 lines).
Checking patch lib/librte_ether/rte_flow.h...
Hunk #1 succeeded at 957 (offset -78 lines).
*Repo: dpdk-next-net
Hunk #3 succeeded at 1456 (offset 12 lines).
Hunk #4 succeeded at 1471 (offset 12 lines).
Checking patch app/test-pmd/testpmd.h...
Hunk #1 succeeded at 618 (offset 2 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

.. table:: Mark, count then redirect

   +-------+--------+-----------+-------+
   | Index | Action | Field     | Value |
--
   +-------+----------------------------+

|


error: patch failed: doc/guides/prog_guide/rte_flow.rst:1153
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch drivers/net/failsafe/failsafe_flow.c...
Checking patch lib/librte_ether/rte_flow.c...
Hunk #1 succeeded at 201 (offset -2 lines).
Checking patch lib/librte_ether/rte_flow.h...
Hunk #1 succeeded at 959 (offset -76 lines).
*Repo: dpdk-next-crypto
Hunk #3 succeeded at 1381 (offset -63 lines).
Hunk #4 succeeded at 1396 (offset -63 lines).
Checking patch app/test-pmd/testpmd.h...
Hunk #1 succeeded at 603 (offset -13 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

.. table:: Mark, count then redirect

   +-------+--------+-----------+-------+
   | Index | Action | Field     | Value |
--
   +-------+----------------------------+

|


error: patch failed: doc/guides/prog_guide/rte_flow.rst:1153
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch drivers/net/failsafe/failsafe_flow.c...
Checking patch lib/librte_ether/rte_flow.c...
Hunk #1 succeeded at 201 (offset -2 lines).
Checking patch lib/librte_ether/rte_flow.h...
Hunk #1 succeeded at 957 (offset -78 lines).
*Repo: dpdk-next-virtio
Hunk #3 succeeded at 1381 (offset -63 lines).
Hunk #4 succeeded at 1396 (offset -63 lines).
Checking patch app/test-pmd/testpmd.h...
Hunk #1 succeeded at 603 (offset -13 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

.. table:: Mark, count then redirect

   +-------+--------+-----------+-------+
   | Index | Action | Field     | Value |
--
   +-------+----------------------------+

|


error: patch failed: doc/guides/prog_guide/rte_flow.rst:1153
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch drivers/net/failsafe/failsafe_flow.c...
Checking patch lib/librte_ether/rte_flow.c...
Hunk #1 succeeded at 201 (offset -2 lines).
Checking patch lib/librte_ether/rte_flow.h...
Hunk #1 succeeded at 957 (offset -78 lines).

DPDK STV team

                 reply	other threads:[~2018-04-25  2:02 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$1g6tfi@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=peipeix.lu@intel.com \
    --cc=test-report@dpdk.org \
    --cc=xinfengx.zhao@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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).