From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw21609 [PATCH v3 1/4] net/tap: add remote netdevice traffic capture
Date: 08 Mar 2017 21:58:00 -0800 [thread overview]
Message-ID: <63cbe6$11v2cv0@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 11394 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21609
_apply patch file failure_
Submitter: Pascal Mazon <pascal.mazon@6wind.com>
Date: Wed, 8 Mar 2017 11:06:44 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a
Repo:dpdk-next-crypto, Branch:master, CommitID:13f57aba3e9f4f6818f525c2e402ac75d5ec7967
Repo:dpdk-next-net, Branch:master, CommitID:ce47e382ceaf2ab0515051cefbd9987c81da4ede
Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
Repo:dpdk, Branch:master, CommitID:c9051455d6bcd4bfdffdc83c8f2c329a7534921c
Apply patch file failed:
Repo: dpdk
21609:
patching file doc/guides/nics/tap.rst
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 56 (offset -7 lines).
Hunk #2 succeeded at 69 (offset -9 lines).
Hunk #3 succeeded at 430 (offset -7 lines).
Hunk #4 succeeded at 476 (offset -7 lines).
Hunk #5 succeeded at 487 (offset -7 lines).
Hunk #6 succeeded at 498 (offset -7 lines).
Hunk #7 succeeded at 509 with fuzz 1 (offset -7 lines).
Hunk #8 FAILED at 643.
Hunk #9 succeeded at 652 with fuzz 1 (offset -207 lines).
Hunk #10 FAILED at 928.
Hunk #11 succeeded at 749 (offset -219 lines).
Hunk #12 succeeded at 771 (offset -219 lines).
Hunk #13 succeeded at 800 (offset -219 lines).
Hunk #14 succeeded at 816 (offset -219 lines).
Hunk #15 FAILED at 1066.
3 out of 15 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 229
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 2c8cc7d5b485..4c4de939f1cc 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 242
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.c b/drivers/net/tap/tap_flow.c
|index 3fb28b1db917..25260570ee50 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
16 out of 16 hunks ignored
can't find file to patch at input line 789
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.h b/drivers/net/tap/tap_flow.h
|index a05e945df523..0134cdbaeb90 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-crypto
21609:
patching file doc/guides/nics/tap.rst
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 56 (offset -7 lines).
Hunk #2 succeeded at 69 (offset -9 lines).
Hunk #3 succeeded at 430 (offset -7 lines).
Hunk #4 succeeded at 476 (offset -7 lines).
Hunk #5 succeeded at 487 (offset -7 lines).
Hunk #6 succeeded at 498 (offset -7 lines).
Hunk #7 succeeded at 509 with fuzz 1 (offset -7 lines).
Hunk #8 FAILED at 643.
Hunk #9 succeeded at 652 with fuzz 1 (offset -207 lines).
Hunk #10 FAILED at 928.
Hunk #11 succeeded at 749 (offset -219 lines).
Hunk #12 succeeded at 771 (offset -219 lines).
Hunk #13 succeeded at 800 (offset -219 lines).
Hunk #14 succeeded at 816 (offset -219 lines).
Hunk #15 FAILED at 1066.
3 out of 15 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 229
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 2c8cc7d5b485..4c4de939f1cc 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 242
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.c b/drivers/net/tap/tap_flow.c
|index 3fb28b1db917..25260570ee50 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
16 out of 16 hunks ignored
can't find file to patch at input line 789
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.h b/drivers/net/tap/tap_flow.h
|index a05e945df523..0134cdbaeb90 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-net
21609:
patching file doc/guides/nics/tap.rst
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 56 (offset -7 lines).
Hunk #2 succeeded at 69 (offset -9 lines).
Hunk #3 succeeded at 430 (offset -7 lines).
Hunk #4 succeeded at 476 (offset -7 lines).
Hunk #5 succeeded at 487 (offset -7 lines).
Hunk #6 succeeded at 498 (offset -7 lines).
Hunk #7 succeeded at 509 with fuzz 1 (offset -7 lines).
Hunk #8 FAILED at 643.
Hunk #9 succeeded at 652 with fuzz 1 (offset -207 lines).
Hunk #10 FAILED at 928.
Hunk #11 succeeded at 750 (offset -218 lines).
Hunk #12 succeeded at 772 (offset -218 lines).
Hunk #13 succeeded at 801 (offset -218 lines).
Hunk #14 succeeded at 817 (offset -218 lines).
Hunk #15 FAILED at 1066.
3 out of 15 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 229
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 2c8cc7d5b485..4c4de939f1cc 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 242
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.c b/drivers/net/tap/tap_flow.c
|index 3fb28b1db917..25260570ee50 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
16 out of 16 hunks ignored
can't find file to patch at input line 789
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.h b/drivers/net/tap/tap_flow.h
|index a05e945df523..0134cdbaeb90 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-virtio
21609:
patching file doc/guides/nics/tap.rst
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 56 (offset -7 lines).
Hunk #2 succeeded at 69 (offset -9 lines).
Hunk #3 succeeded at 430 (offset -7 lines).
Hunk #4 succeeded at 476 (offset -7 lines).
Hunk #5 succeeded at 487 (offset -7 lines).
Hunk #6 succeeded at 498 (offset -7 lines).
Hunk #7 succeeded at 509 with fuzz 1 (offset -7 lines).
Hunk #8 FAILED at 643.
Hunk #9 succeeded at 652 with fuzz 1 (offset -207 lines).
Hunk #10 FAILED at 928.
Hunk #11 succeeded at 749 (offset -219 lines).
Hunk #12 succeeded at 771 (offset -219 lines).
Hunk #13 succeeded at 800 (offset -219 lines).
Hunk #14 succeeded at 816 (offset -219 lines).
Hunk #15 FAILED at 1066.
3 out of 15 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 229
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 2c8cc7d5b485..4c4de939f1cc 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 242
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.c b/drivers/net/tap/tap_flow.c
|index 3fb28b1db917..25260570ee50 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
16 out of 16 hunks ignored
can't find file to patch at input line 789
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.h b/drivers/net/tap/tap_flow.h
|index a05e945df523..0134cdbaeb90 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-eventdev
21609:
patching file doc/guides/nics/tap.rst
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 56 (offset -7 lines).
Hunk #2 succeeded at 69 (offset -9 lines).
Hunk #3 succeeded at 430 (offset -7 lines).
Hunk #4 succeeded at 476 (offset -7 lines).
Hunk #5 succeeded at 487 (offset -7 lines).
Hunk #6 succeeded at 498 (offset -7 lines).
Hunk #7 succeeded at 509 with fuzz 1 (offset -7 lines).
Hunk #8 FAILED at 643.
Hunk #9 succeeded at 652 with fuzz 1 (offset -207 lines).
Hunk #10 FAILED at 928.
Hunk #11 succeeded at 749 (offset -219 lines).
Hunk #12 succeeded at 771 (offset -219 lines).
Hunk #13 succeeded at 800 (offset -219 lines).
Hunk #14 succeeded at 816 (offset -219 lines).
Hunk #15 FAILED at 1066.
3 out of 15 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 229
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 2c8cc7d5b485..4c4de939f1cc 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 242
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.c b/drivers/net/tap/tap_flow.c
|index 3fb28b1db917..25260570ee50 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
16 out of 16 hunks ignored
can't find file to patch at input line 789
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap_flow.h b/drivers/net/tap/tap_flow.h
|index a05e945df523..0134cdbaeb90 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
DPDK STV team
reply other threads:[~2017-03-09 5:58 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='63cbe6$11v2cv0@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=pascal.mazon@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).