automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw40934[dpdk-dev, v1, 1/4] eventdev: standardize Rx adapter internal function names
Date: 08 Jun 2018 11:19:20 -0700	[thread overview]
Message-ID: <0590c7$1s21jm@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Nikhil Rao <nikhil.rao@intel.com>
Date: 2018-06-08 18:15:14
DPDK git baseline:
	Repo:dpdk-master, CommitID: b259da7b24e75b967e63f549177e507163719d1a
	Repo:dpdk-next-eventdev, CommitID: 82141ea88c726d320373069fe9064b321baf990d
	Repo:dpdk-next-net, CommitID: e6ec35424011de781b29739fa9618d8f9b9cfd97
	Repo:dpdk-next-crypto, CommitID: b259da7b24e75b967e63f549177e507163719d1a
	Repo:dpdk-next-virtio, CommitID: bdb72af7a66730d71ff7e2078533f5cd7376326d

*Repo: dpdk-master
Hunk #9 succeeded at 339 (offset -4 lines).
Hunk #10 succeeded at 358 (offset -4 lines).
Hunk #11 succeeded at 380 (offset -4 lines).
Hunk #12 succeeded at 390 (offset -4 lines).
Hunk #13 succeeded at 407 (offset -4 lines).
error: while searching for:
}

static inline void
fill_event_buffer(struct rte_event_eth_rx_adapter *rx_adapter,
	uint16_t eth_dev_id,
--
	uint16_t num)
{
	uint32_t i;
	struct eth_device_info *eth_device_info =

error: patch failed: lib/librte_eventdev/rte_event_eth_rx_adapter.c:421
error: lib/librte_eventdev/rte_event_eth_rx_adapter.c: patch does not apply
*Repo: dpdk-next-eventdev
Hunk #12 succeeded at 390 (offset -4 lines).
Hunk #13 succeeded at 407 (offset -4 lines).
Hunk #14 succeeded at 417 (offset -4 lines).
Hunk #15 succeeded at 459 (offset -4 lines).
Hunk #16 succeeded at 474 (offset -4 lines).
error: while searching for:
 * it.
 */
static inline void
eth_rx_poll(struct rte_event_eth_rx_adapter *rx_adapter)
{
	uint32_t num_queue;
	uint16_t n;

error: patch failed: lib/librte_eventdev/rte_event_eth_rx_adapter.c:495
error: lib/librte_eventdev/rte_event_eth_rx_adapter.c: patch does not apply
*Repo: dpdk-next-net
Hunk #9 succeeded at 339 (offset -4 lines).
Hunk #10 succeeded at 358 (offset -4 lines).
Hunk #11 succeeded at 380 (offset -4 lines).
Hunk #12 succeeded at 390 (offset -4 lines).
Hunk #13 succeeded at 407 (offset -4 lines).
error: while searching for:
}

static inline void
fill_event_buffer(struct rte_event_eth_rx_adapter *rx_adapter,
	uint16_t eth_dev_id,
--
	uint16_t num)
{
	uint32_t i;
	struct eth_device_info *eth_device_info =

error: patch failed: lib/librte_eventdev/rte_event_eth_rx_adapter.c:421
error: lib/librte_eventdev/rte_event_eth_rx_adapter.c: patch does not apply
*Repo: dpdk-next-crypto
Hunk #9 succeeded at 339 (offset -4 lines).
Hunk #10 succeeded at 358 (offset -4 lines).
Hunk #11 succeeded at 380 (offset -4 lines).
Hunk #12 succeeded at 390 (offset -4 lines).
Hunk #13 succeeded at 407 (offset -4 lines).
error: while searching for:
}

static inline void
fill_event_buffer(struct rte_event_eth_rx_adapter *rx_adapter,
	uint16_t eth_dev_id,
--
	uint16_t num)
{
	uint32_t i;
	struct eth_device_info *eth_device_info =

error: patch failed: lib/librte_eventdev/rte_event_eth_rx_adapter.c:421
error: lib/librte_eventdev/rte_event_eth_rx_adapter.c: patch does not apply
*Repo: dpdk-next-virtio
Hunk #9 succeeded at 339 (offset -4 lines).
Hunk #10 succeeded at 358 (offset -4 lines).
Hunk #11 succeeded at 380 (offset -4 lines).
Hunk #12 succeeded at 390 (offset -4 lines).
Hunk #13 succeeded at 407 (offset -4 lines).
error: while searching for:
}

static inline void
fill_event_buffer(struct rte_event_eth_rx_adapter *rx_adapter,
	uint16_t eth_dev_id,
--
	uint16_t num)
{
	uint32_t i;
	struct eth_device_info *eth_device_info =

error: patch failed: lib/librte_eventdev/rte_event_eth_rx_adapter.c:421
error: lib/librte_eventdev/rte_event_eth_rx_adapter.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2018-06-08 18:19 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$1s21jm@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).