From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw38515 [PATCH v5 16/16] ethdev: add port ID item and action to flow API
Date: 02 May 2018 19:52:32 -0700 [thread overview]
Message-ID: <ca5293$1hhto2@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 8112 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38515
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Thu, 19 Apr 2018 12:16:43 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc
Repo:dpdk-next-net, Branch:master, CommitID:36decb6967e0563430a6e3ab0e2db3fe4ccc8db2
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:7baac775945ce26f4740158656965f095dc4dbda
Apply patch file failed:
Repo: dpdk
38515:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 FAILED at 89.
Hunk #2 FAILED at 185.
Hunk #3 FAILED at 445.
Hunk #4 succeeded at 564 (offset 73 lines).
Hunk #5 FAILED at 633.
Hunk #6 succeeded at 833 (offset 159 lines).
Hunk #7 succeeded at 1331 with fuzz 2 (offset 234 lines).
Hunk #8 succeeded at 2247 (offset 471 lines).
4 out of 8 hunks FAILED -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file app/test-pmd/config.c.rej
patching file doc/guides/prog_guide/rte_flow.rst
Hunk #1 succeeded at 686 with fuzz 2 (offset 69 lines).
Hunk #2 succeeded at 1761 (offset 278 lines).
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
Hunk #1 succeeded at 3244 with fuzz 2 (offset 32 lines).
Hunk #2 succeeded at 3563 (offset 131 lines).
can't find file to patch at input line 235
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.c b/lib/librte_ether/rte_flow.c
|index 00989c73b..cecab59f6 100644
|--- a/lib/librte_ether/rte_flow.c
|+++ b/lib/librte_ether/rte_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 255
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.h b/lib/librte_ether/rte_flow.h
|index 58b75e934..09a21e531 100644
|--- a/lib/librte_ether/rte_flow.h
|+++ b/lib/librte_ether/rte_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
Repo: dpdk-next-crypto
38515:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 FAILED at 89.
Hunk #2 FAILED at 185.
Hunk #3 FAILED at 445.
Hunk #4 succeeded at 564 (offset 73 lines).
Hunk #5 FAILED at 633.
Hunk #6 succeeded at 833 (offset 159 lines).
Hunk #7 succeeded at 1331 with fuzz 2 (offset 234 lines).
Hunk #8 succeeded at 2247 (offset 471 lines).
4 out of 8 hunks FAILED -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file app/test-pmd/config.c.rej
patching file doc/guides/prog_guide/rte_flow.rst
Hunk #1 succeeded at 686 with fuzz 2 (offset 69 lines).
Hunk #2 succeeded at 1761 (offset 278 lines).
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
Hunk #1 succeeded at 3244 with fuzz 2 (offset 32 lines).
Hunk #2 succeeded at 3563 (offset 131 lines).
can't find file to patch at input line 235
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.c b/lib/librte_ether/rte_flow.c
|index 00989c73b..cecab59f6 100644
|--- a/lib/librte_ether/rte_flow.c
|+++ b/lib/librte_ether/rte_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 255
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.h b/lib/librte_ether/rte_flow.h
|index 58b75e934..09a21e531 100644
|--- a/lib/librte_ether/rte_flow.h
|+++ b/lib/librte_ether/rte_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
Repo: dpdk-next-net
38515:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 FAILED at 89.
Hunk #2 FAILED at 185.
Hunk #3 FAILED at 445.
Hunk #4 succeeded at 564 (offset 73 lines).
Hunk #5 FAILED at 633.
Hunk #6 succeeded at 833 (offset 159 lines).
Hunk #7 succeeded at 1331 with fuzz 2 (offset 234 lines).
Hunk #8 succeeded at 2247 (offset 471 lines).
4 out of 8 hunks FAILED -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file app/test-pmd/config.c.rej
patching file doc/guides/prog_guide/rte_flow.rst
Hunk #1 succeeded at 686 with fuzz 2 (offset 69 lines).
Hunk #2 succeeded at 1761 (offset 278 lines).
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
Hunk #1 succeeded at 3244 with fuzz 2 (offset 32 lines).
Hunk #2 succeeded at 3563 (offset 131 lines).
can't find file to patch at input line 235
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.c b/lib/librte_ether/rte_flow.c
|index 00989c73b..cecab59f6 100644
|--- a/lib/librte_ether/rte_flow.c
|+++ b/lib/librte_ether/rte_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 255
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.h b/lib/librte_ether/rte_flow.h
|index 58b75e934..09a21e531 100644
|--- a/lib/librte_ether/rte_flow.h
|+++ b/lib/librte_ether/rte_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
Repo: dpdk-next-eventdev
38515:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 FAILED at 89.
Hunk #2 FAILED at 185.
Hunk #3 FAILED at 445.
Hunk #4 succeeded at 564 (offset 73 lines).
Hunk #5 FAILED at 633.
Hunk #6 succeeded at 833 (offset 159 lines).
Hunk #7 succeeded at 1331 with fuzz 2 (offset 234 lines).
Hunk #8 succeeded at 2247 (offset 471 lines).
4 out of 8 hunks FAILED -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file app/test-pmd/config.c.rej
patching file doc/guides/prog_guide/rte_flow.rst
Hunk #1 succeeded at 686 with fuzz 2 (offset 69 lines).
Hunk #2 succeeded at 1761 (offset 278 lines).
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
Hunk #1 succeeded at 3244 with fuzz 2 (offset 32 lines).
Hunk #2 succeeded at 3563 (offset 131 lines).
can't find file to patch at input line 235
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.c b/lib/librte_ether/rte_flow.c
|index 00989c73b..cecab59f6 100644
|--- a/lib/librte_ether/rte_flow.c
|+++ b/lib/librte_ether/rte_flow.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 255
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_ether/rte_flow.h b/lib/librte_ether/rte_flow.h
|index 58b75e934..09a21e531 100644
|--- a/lib/librte_ether/rte_flow.h
|+++ b/lib/librte_ether/rte_flow.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
DPDK STV team
reply other threads:[~2018-05-03 2: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='ca5293$1hhto2@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=adrien.mazarguil@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).