From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw36466 [PATCH 1/2] kvargs: the life of the party
Date: 23 Mar 2018 12:19:33 -0700 [thread overview]
Message-ID: <ca5293$16pi3b@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7135 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36466
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Fri, 23 Mar 2018 19:45:02 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:34184d9779e0aa56ab841bb2502b8945e91d8cac
Repo:dpdk-next-crypto, Branch:master, CommitID:7964ded554f3e02a62e8e9a92b9760d0de51346f
Repo:dpdk-next-net, Branch:master, CommitID:b83df31376fdd2652f1b557829211f81f131a81c
Repo:dpdk-next-virtio, Branch:master, CommitID:fc33e147ae5e63a28c2b2c9bec5ad378c612ca36
Repo:dpdk, Branch:master, CommitID:8f0b534b35a6748563e953ef40112bbb750f354c
Apply patch file failed:
Repo: dpdk
36466:
patching file drivers/baseband/Makefile
patching file lib/Makefile
Hunk #1 FAILED at 20.
1 out of 2 hunks FAILED -- saving rejects to file lib/Makefile.rej
patching file lib/librte_eal/Makefile
patching file lib/librte_eal/common/Makefile
Hunk #1 succeeded at 9 with fuzz 2.
patching file lib/librte_eal/kvargs/Makefile
patching file lib/librte_eal/kvargs/meson.build (renamed from lib/librte_kvargs/meson.build)
patching file lib/librte_eal/kvargs/rte_kvargs.c (renamed from lib/librte_kvargs/rte_kvargs.c)
patching file lib/librte_eal/kvargs/rte_kvargs.h (renamed from lib/librte_kvargs/rte_kvargs.h)
patching file lib/librte_eal/kvargs/rte_kvargs_version.map (renamed from lib/librte_kvargs/rte_kvargs_version.map)
patching file lib/librte_eal/kvargs/rte_string_fns.h (renamed from lib/librte_eal/common/include/rte_string_fns.h)
patching file lib/librte_eal/linuxapp/eal/eal_hugepage_info.c
patching file lib/librte_kvargs/Makefile
Repo: dpdk-next-crypto
36466:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/baseband/Makefile b/drivers/baseband/Makefile
|index 4ec83b0a0..64f6f9ca7 100644
|--- a/drivers/baseband/Makefile
|+++ b/drivers/baseband/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/Makefile
Hunk #1 FAILED at 20.
1 out of 2 hunks FAILED -- saving rejects to file lib/Makefile.rej
patching file lib/librte_eal/Makefile
patching file lib/librte_eal/common/Makefile
Hunk #1 succeeded at 9 with fuzz 2.
patching file lib/librte_eal/kvargs/Makefile
patching file lib/librte_eal/kvargs/meson.build (renamed from lib/librte_kvargs/meson.build)
patching file lib/librte_eal/kvargs/rte_kvargs.c (renamed from lib/librte_kvargs/rte_kvargs.c)
patching file lib/librte_eal/kvargs/rte_kvargs.h (renamed from lib/librte_kvargs/rte_kvargs.h)
patching file lib/librte_eal/kvargs/rte_kvargs_version.map (renamed from lib/librte_kvargs/rte_kvargs_version.map)
patching file lib/librte_eal/kvargs/rte_string_fns.h (renamed from lib/librte_eal/common/include/rte_string_fns.h)
patching file lib/librte_eal/linuxapp/eal/eal_hugepage_info.c
patching file lib/librte_kvargs/Makefile
Repo: dpdk-next-net
36466:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/baseband/Makefile b/drivers/baseband/Makefile
|index 4ec83b0a0..64f6f9ca7 100644
|--- a/drivers/baseband/Makefile
|+++ b/drivers/baseband/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/Makefile
Hunk #1 FAILED at 20.
1 out of 2 hunks FAILED -- saving rejects to file lib/Makefile.rej
patching file lib/librte_eal/Makefile
patching file lib/librte_eal/common/Makefile
Hunk #1 succeeded at 9 with fuzz 2.
patching file lib/librte_eal/kvargs/Makefile
patching file lib/librte_eal/kvargs/meson.build (renamed from lib/librte_kvargs/meson.build)
patching file lib/librte_eal/kvargs/rte_kvargs.c (renamed from lib/librte_kvargs/rte_kvargs.c)
patching file lib/librte_eal/kvargs/rte_kvargs.h (renamed from lib/librte_kvargs/rte_kvargs.h)
patching file lib/librte_eal/kvargs/rte_kvargs_version.map (renamed from lib/librte_kvargs/rte_kvargs_version.map)
patching file lib/librte_eal/kvargs/rte_string_fns.h (renamed from lib/librte_eal/common/include/rte_string_fns.h)
patching file lib/librte_eal/linuxapp/eal/eal_hugepage_info.c
patching file lib/librte_kvargs/Makefile
Repo: dpdk-next-virtio
36466:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/baseband/Makefile b/drivers/baseband/Makefile
|index 4ec83b0a0..64f6f9ca7 100644
|--- a/drivers/baseband/Makefile
|+++ b/drivers/baseband/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/Makefile
Hunk #1 FAILED at 20.
1 out of 2 hunks FAILED -- saving rejects to file lib/Makefile.rej
patching file lib/librte_eal/Makefile
patching file lib/librte_eal/common/Makefile
Hunk #1 succeeded at 9 with fuzz 2.
patching file lib/librte_eal/kvargs/Makefile
patching file lib/librte_eal/kvargs/meson.build (renamed from lib/librte_kvargs/meson.build)
patching file lib/librte_eal/kvargs/rte_kvargs.c (renamed from lib/librte_kvargs/rte_kvargs.c)
patching file lib/librte_eal/kvargs/rte_kvargs.h (renamed from lib/librte_kvargs/rte_kvargs.h)
patching file lib/librte_eal/kvargs/rte_kvargs_version.map (renamed from lib/librte_kvargs/rte_kvargs_version.map)
patching file lib/librte_eal/kvargs/rte_string_fns.h (renamed from lib/librte_eal/common/include/rte_string_fns.h)
patching file lib/librte_eal/linuxapp/eal/eal_hugepage_info.c
patching file lib/librte_kvargs/Makefile
Repo: dpdk-next-eventdev
36466:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/baseband/Makefile b/drivers/baseband/Makefile
|index 4ec83b0a0..64f6f9ca7 100644
|--- a/drivers/baseband/Makefile
|+++ b/drivers/baseband/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/Makefile
Hunk #1 FAILED at 20.
1 out of 2 hunks FAILED -- saving rejects to file lib/Makefile.rej
patching file lib/librte_eal/Makefile
patching file lib/librte_eal/common/Makefile
Hunk #1 succeeded at 9 with fuzz 2.
patching file lib/librte_eal/kvargs/Makefile
patching file lib/librte_eal/kvargs/meson.build (renamed from lib/librte_kvargs/meson.build)
patching file lib/librte_eal/kvargs/rte_kvargs.c (renamed from lib/librte_kvargs/rte_kvargs.c)
patching file lib/librte_eal/kvargs/rte_kvargs.h (renamed from lib/librte_kvargs/rte_kvargs.h)
patching file lib/librte_eal/kvargs/rte_kvargs_version.map (renamed from lib/librte_kvargs/rte_kvargs_version.map)
patching file lib/librte_eal/kvargs/rte_string_fns.h (renamed from lib/librte_eal/common/include/rte_string_fns.h)
patching file lib/librte_eal/linuxapp/eal/eal_hugepage_info.c
patching file lib/librte_kvargs/Makefile
DPDK STV team
reply other threads:[~2018-03-23 19:19 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$16pi3b@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gaetan.rivet@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).