From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw23539 [PATCH v2 12/42] net/bonding: make bonding API call through EAL on create/free
Date: 12 Apr 2017 08:52:42 -0700 [thread overview]
Message-ID: <e81775$11pud0i@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3056 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23539
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Tue, 11 Apr 2017 17:44:19 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:41c63e15eb931fee8e52e36570cab79a9817b960
Repo:dpdk-next-net, Branch:master, CommitID:ca5631528390a1ead73a98e4cea1876d0490edb6
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:4b6fa6d32d2acfce5960522ba904929ee5274eb7
Apply patch file failed:
Repo: dpdk
23539:
patching file drivers/net/bonding/rte_eth_bond_api.c
patching file drivers/net/bonding/rte_eth_bond_args.c
patching file drivers/net/bonding/rte_eth_bond_pmd.c
Hunk #2 FAILED at 2241.
Hunk #3 FAILED at 2249.
Hunk #4 succeeded at 2287 (offset -3 lines).
Hunk #5 FAILED at 2315.
Hunk #6 succeeded at 2319 with fuzz 1 (offset -5 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/bonding/rte_eth_bond_pmd.c.rej
Repo: dpdk-next-crypto
23539:
patching file drivers/net/bonding/rte_eth_bond_api.c
patching file drivers/net/bonding/rte_eth_bond_args.c
patching file drivers/net/bonding/rte_eth_bond_pmd.c
Hunk #2 FAILED at 2241.
Hunk #3 FAILED at 2249.
Hunk #4 succeeded at 2287 (offset -3 lines).
Hunk #5 FAILED at 2315.
Hunk #6 succeeded at 2319 with fuzz 1 (offset -5 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/bonding/rte_eth_bond_pmd.c.rej
Repo: dpdk-next-net
23539:
patching file drivers/net/bonding/rte_eth_bond_api.c
patching file drivers/net/bonding/rte_eth_bond_args.c
patching file drivers/net/bonding/rte_eth_bond_pmd.c
Hunk #2 FAILED at 2241.
Hunk #3 FAILED at 2249.
Hunk #4 succeeded at 2287 (offset -3 lines).
Hunk #5 FAILED at 2315.
Hunk #6 succeeded at 2319 with fuzz 1 (offset -5 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/bonding/rte_eth_bond_pmd.c.rej
Repo: dpdk-next-virtio
23539:
patching file drivers/net/bonding/rte_eth_bond_api.c
patching file drivers/net/bonding/rte_eth_bond_args.c
patching file drivers/net/bonding/rte_eth_bond_pmd.c
Hunk #2 FAILED at 2241.
Hunk #3 FAILED at 2249.
Hunk #4 succeeded at 2287 (offset -3 lines).
Hunk #5 FAILED at 2315.
Hunk #6 succeeded at 2319 with fuzz 1 (offset -5 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/bonding/rte_eth_bond_pmd.c.rej
Repo: dpdk-next-eventdev
23539:
patching file drivers/net/bonding/rte_eth_bond_api.c
patching file drivers/net/bonding/rte_eth_bond_args.c
patching file drivers/net/bonding/rte_eth_bond_pmd.c
Hunk #2 FAILED at 2241.
Hunk #3 FAILED at 2249.
Hunk #4 succeeded at 2278 (offset -12 lines).
Hunk #5 FAILED at 2315.
Hunk #6 succeeded at 2310 with fuzz 1 (offset -14 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/bonding/rte_eth_bond_pmd.c.rej
DPDK STV team
reply other threads:[~2017-04-12 15:52 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='e81775$11pud0i@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gaetan.rivet@6wind.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).