[dpdk-test-report] |FAILURE| pw21513 [PATCH v2 4/4] net/tap: add basic flow API patterns and actions

sys_stv at intel.com sys_stv at intel.com
Wed Mar 8 18:56:42 CET 2017


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

_apply patch file failure_

Submitter: Pascal Mazon <pascal.mazon at 6wind.com>
Date: Mon,  6 Mar 2017 18:05:30 +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
21513:
patching file drivers/net/tap/Makefile
Hunk #1 FAILED at 41.
Hunk #2 succeeded at 53 (offset -4 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/tap/Makefile.rej
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 112 with fuzz 1 (offset 26 lines).
Hunk #3 FAILED at 596.
Hunk #4 succeeded at 643 (offset -152 lines).
Hunk #5 FAILED at 869.
Hunk #6 succeeded at 828 with fuzz 1 (offset -158 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 177
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 60c0c58c7c1a..db157c60d1cb 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 190
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 de41c127c920..9c299d82c00b 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 1183
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 377a9f7b758a..a05e945df523 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored

Repo: dpdk-next-crypto
21513:
patching file drivers/net/tap/Makefile
Hunk #1 FAILED at 41.
Hunk #2 succeeded at 53 (offset -4 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/tap/Makefile.rej
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 112 with fuzz 1 (offset 26 lines).
Hunk #3 FAILED at 596.
Hunk #4 succeeded at 643 (offset -152 lines).
Hunk #5 FAILED at 869.
Hunk #6 succeeded at 828 with fuzz 1 (offset -158 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 177
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 60c0c58c7c1a..db157c60d1cb 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 190
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 de41c127c920..9c299d82c00b 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 1183
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 377a9f7b758a..a05e945df523 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored

Repo: dpdk-next-net
21513:
patching file drivers/net/tap/Makefile
Hunk #1 FAILED at 41.
Hunk #2 succeeded at 53 (offset -4 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/tap/Makefile.rej
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 112 with fuzz 1 (offset 26 lines).
Hunk #3 FAILED at 596.
Hunk #4 succeeded at 643 (offset -152 lines).
Hunk #5 FAILED at 869.
Hunk #6 succeeded at 829 with fuzz 1 (offset -157 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 177
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 60c0c58c7c1a..db157c60d1cb 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 190
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 de41c127c920..9c299d82c00b 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 1183
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 377a9f7b758a..a05e945df523 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored

Repo: dpdk-next-virtio
21513:
patching file drivers/net/tap/Makefile
Hunk #1 FAILED at 41.
Hunk #2 succeeded at 53 (offset -4 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/tap/Makefile.rej
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 112 with fuzz 1 (offset 26 lines).
Hunk #3 FAILED at 596.
Hunk #4 succeeded at 643 (offset -152 lines).
Hunk #5 FAILED at 869.
Hunk #6 succeeded at 828 with fuzz 1 (offset -158 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 177
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 60c0c58c7c1a..db157c60d1cb 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 190
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 de41c127c920..9c299d82c00b 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 1183
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 377a9f7b758a..a05e945df523 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored

Repo: dpdk-next-eventdev
21513:
patching file drivers/net/tap/Makefile
Hunk #1 FAILED at 41.
Hunk #2 succeeded at 53 (offset -4 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/tap/Makefile.rej
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 112 with fuzz 1 (offset 26 lines).
Hunk #3 FAILED at 596.
Hunk #4 succeeded at 643 (offset -152 lines).
Hunk #5 FAILED at 869.
Hunk #6 succeeded at 828 with fuzz 1 (offset -158 lines).
3 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 177
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 60c0c58c7c1a..db157c60d1cb 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 190
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 de41c127c920..9c299d82c00b 100644
|--- a/drivers/net/tap/tap_flow.c
|+++ b/drivers/net/tap/tap_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 1183
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 377a9f7b758a..a05e945df523 100644
|--- a/drivers/net/tap/tap_flow.h
|+++ b/drivers/net/tap/tap_flow.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored


DPDK STV team


More information about the test-report mailing list