From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: keith.wiles@intel.com
Subject: [dpdk-test-report] |FAILURE| pw20173 [PATCH v2 4/6] net/tap: fix multi-queue support
Date: 05 Feb 2017 10:01:25 -0800 [thread overview]
Message-ID: <e81775$10s7ona@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2823 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/20173
_apply patch file failure_
Submitter: Keith Wiles <keith.wiles@intel.com>
Date: Sun, 5 Feb 2017 10:05:07 -0600
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:f13b12ef54e21fe166ea5fc256d80becf3f8b2db
Repo:dpdk-next-crypto, Branch:master, CommitID:5b243cbab26652027c3848e35fe595025f3622ea
Repo:dpdk-next-net, Branch:master, CommitID:193b5df8011470892fd9f6c93081c5d5986be188
Repo:dpdk-next-virtio, Branch:master, CommitID:a69de21ee881adb095667a15a28fbf5044e22a28
Repo:dpdk, Branch:master, CommitID:5b243cbab26652027c3848e35fe595025f3622ea
Apply patch file failed:
Repo: dpdk
20173:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 119 (offset 1 line).
Hunk #3 succeeded at 140 (offset 1 line).
Hunk #4 succeeded at 174 (offset 1 line).
Hunk #5 FAILED at 509.
Hunk #6 FAILED at 631.
Hunk #7 succeeded at 606 with fuzz 1 (offset -70 lines).
Hunk #8 FAILED at 706.
3 out of 8 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-crypto
20173:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 119 (offset 1 line).
Hunk #3 succeeded at 140 (offset 1 line).
Hunk #4 succeeded at 174 (offset 1 line).
Hunk #5 FAILED at 509.
Hunk #6 FAILED at 631.
Hunk #7 succeeded at 606 with fuzz 1 (offset -70 lines).
Hunk #8 FAILED at 706.
3 out of 8 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-net
20173:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 119 (offset 1 line).
Hunk #3 succeeded at 140 (offset 1 line).
Hunk #4 succeeded at 174 (offset 1 line).
Hunk #5 succeeded at 514 (offset 5 lines).
Hunk #6 FAILED at 631.
Hunk #7 succeeded at 682 (offset 6 lines).
Hunk #8 FAILED at 706.
2 out of 8 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-virtio
20173:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 119 (offset 1 line).
Hunk #3 succeeded at 140 (offset 1 line).
Hunk #4 succeeded at 174 (offset 1 line).
Hunk #5 FAILED at 509.
Hunk #6 FAILED at 631.
Hunk #7 succeeded at 588 with fuzz 1 (offset -88 lines).
Hunk #8 FAILED at 706.
3 out of 8 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-eventdev
20173:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 119 (offset 1 line).
Hunk #3 succeeded at 140 (offset 1 line).
Hunk #4 succeeded at 174 (offset 1 line).
Hunk #5 FAILED at 509.
Hunk #6 FAILED at 631.
Hunk #7 succeeded at 606 with fuzz 1 (offset -70 lines).
Hunk #8 FAILED at 706.
3 out of 8 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
DPDK STV team
reply other threads:[~2017-02-05 18:01 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$10s7ona@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=keith.wiles@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).