From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-test-report] |FAILURE| pw34202 [PATCH v6 4/4] ethdev: rename function parameter for consistency
Date: 22 Jan 2018 11:50:21 -0800 [thread overview]
Message-ID: <f7a79a$r6s4n@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/34202
_apply patch file failure_
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Mon, 22 Jan 2018 00:16:23 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18daa7305ffd89b443cf56694fd30790cca0d3ce
Repo:dpdk-next-crypto, Branch:master, CommitID:d3091b0f880e35ca8d5fb4f8385de055bb7f450d
Repo:dpdk-next-net, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
Repo:dpdk-next-virtio, Branch:master, CommitID:dd854ceec2e09a93f2509de03ae6d67e201b1a2b
Repo:dpdk, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
Apply patch file failed:
Repo: dpdk-next-virtio
34202:
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 1620 (offset 462 lines).
Hunk #2 succeeded at 1636 (offset 462 lines).
Hunk #3 succeeded at 1646 (offset 462 lines).
Hunk #4 succeeded at 1660 (offset 462 lines).
Hunk #5 succeeded at 3657 (offset 1086 lines).
Hunk #6 FAILED at 2579.
Hunk #7 succeeded at 3687 (offset 1085 lines).
Hunk #8 succeeded at 3702 (offset 1085 lines).
Hunk #9 succeeded at 3720 with fuzz 2 (offset 1084 lines).
Hunk #10 succeeded at 3739 with fuzz 2 (offset 1083 lines).
Hunk #11 succeeded at 3748 (offset 1083 lines).
Hunk #12 succeeded at 3761 with fuzz 1 (offset 1082 lines).
Hunk #13 succeeded at 3769 (offset 1082 lines).
Hunk #14 succeeded at 3781 with fuzz 1 (offset 1081 lines).
1 out of 14 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.h.rej
Repo: dpdk-next-eventdev
34202:
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 1620 (offset 462 lines).
Hunk #2 succeeded at 1636 (offset 462 lines).
Hunk #3 succeeded at 1646 (offset 462 lines).
Hunk #4 succeeded at 1660 (offset 462 lines).
Hunk #5 succeeded at 3657 (offset 1086 lines).
Hunk #6 FAILED at 2579.
Hunk #7 succeeded at 3687 (offset 1085 lines).
Hunk #8 succeeded at 3702 (offset 1085 lines).
Hunk #9 succeeded at 3720 with fuzz 2 (offset 1084 lines).
Hunk #10 succeeded at 3739 with fuzz 2 (offset 1083 lines).
Hunk #11 succeeded at 3748 (offset 1083 lines).
Hunk #12 succeeded at 3761 with fuzz 1 (offset 1082 lines).
Hunk #13 succeeded at 3769 (offset 1082 lines).
Hunk #14 succeeded at 3781 with fuzz 1 (offset 1081 lines).
1 out of 14 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.h.rej
DPDK STV team
reply other threads:[~2018-01-22 19:50 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='f7a79a$r6s4n@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=ferruh.yigit@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).