From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: allain.legacy@windriver.com
Subject: [dpdk-test-report] |FAILURE| pw22655 [PATCH v3 3/6] cfgfile: add support for configurable comment character
Date: 29 Mar 2017 08:26:51 -0700 [thread overview]
Message-ID: <e81775$11k7n6j@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5035 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22655
_apply patch file failure_
Submitter: Allain Legacy <allain.legacy@windriver.com>
Date: Tue, 28 Mar 2017 20:47:34 -0400
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
Repo:dpdk-next-crypto, Branch:master, CommitID:3eacd5a3ef2aa2f811b943659560c37fbd332b84
Repo:dpdk-next-net, Branch:master, CommitID:d1f78e9696cd39a5faed498ad7e8368c724945e4
Repo:dpdk-next-virtio, Branch:master, CommitID:8ec4aa31199c361151610ef54427d5f91c3dac8c
Repo:dpdk, Branch:master, CommitID:05cc9fec458ca6fb316342246f4775591988088e
Apply patch file failed:
Repo: dpdk
22655:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #5 succeeded at 175 (offset -16 lines).
patching file lib/librte_cfgfile/rte_cfgfile.h
Hunk #1 FAILED at 66.
Hunk #2 succeeded at 78 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 82 (offset -8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.h.rej
can't find file to patch at input line 162
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_cfgfile.c b/test/test/test_cfgfile.c
|index ad293cc89..0478de59e 100644
|--- a/test/test/test_cfgfile.c
|+++ b/test/test/test_cfgfile.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
3 out of 3 hunks ignored
patching file test/test/test_cfgfiles/etc/sample2.ini
Repo: dpdk-next-crypto
22655:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #5 succeeded at 175 (offset -16 lines).
patching file lib/librte_cfgfile/rte_cfgfile.h
Hunk #1 FAILED at 66.
Hunk #2 succeeded at 78 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 82 (offset -8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.h.rej
can't find file to patch at input line 162
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_cfgfile.c b/test/test/test_cfgfile.c
|index ad293cc89..0478de59e 100644
|--- a/test/test/test_cfgfile.c
|+++ b/test/test/test_cfgfile.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
3 out of 3 hunks ignored
patching file test/test/test_cfgfiles/etc/sample2.ini
Repo: dpdk-next-net
22655:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #5 succeeded at 175 (offset -16 lines).
patching file lib/librte_cfgfile/rte_cfgfile.h
Hunk #1 FAILED at 66.
Hunk #2 succeeded at 78 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 82 (offset -8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.h.rej
can't find file to patch at input line 162
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_cfgfile.c b/test/test/test_cfgfile.c
|index ad293cc89..0478de59e 100644
|--- a/test/test/test_cfgfile.c
|+++ b/test/test/test_cfgfile.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
3 out of 3 hunks ignored
patching file test/test/test_cfgfiles/etc/sample2.ini
Repo: dpdk-next-virtio
22655:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #5 succeeded at 175 (offset -16 lines).
patching file lib/librte_cfgfile/rte_cfgfile.h
Hunk #1 FAILED at 66.
Hunk #2 succeeded at 78 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 82 (offset -8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.h.rej
can't find file to patch at input line 162
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_cfgfile.c b/test/test/test_cfgfile.c
|index ad293cc89..0478de59e 100644
|--- a/test/test/test_cfgfile.c
|+++ b/test/test/test_cfgfile.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
3 out of 3 hunks ignored
patching file test/test/test_cfgfiles/etc/sample2.ini
Repo: dpdk-next-eventdev
22655:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #5 succeeded at 175 (offset -16 lines).
patching file lib/librte_cfgfile/rte_cfgfile.h
Hunk #1 FAILED at 66.
Hunk #2 succeeded at 78 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 82 (offset -8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.h.rej
can't find file to patch at input line 162
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_cfgfile.c b/test/test/test_cfgfile.c
|index ad293cc89..0478de59e 100644
|--- a/test/test/test_cfgfile.c
|+++ b/test/test/test_cfgfile.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
3 out of 3 hunks ignored
patching file test/test/test_cfgfiles/etc/sample2.ini
DPDK STV team
reply other threads:[~2017-03-29 15:26 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$11k7n6j@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=allain.legacy@windriver.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).