From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gregory@weka.io
Subject: [dpdk-test-report] |FAILURE| pw17776 [PATCH] IGB_UIO: PCI Resources Management
Date: 09 Dec 2016 01:16:33 -0800 [thread overview]
Message-ID: <587443$f2pis@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3263 bytes --]
Test-Label: Intel Per-patch compilation check
Test-Status: FAILURE
Patchwork ID: 17776
http://www.dpdk.org/dev/patchwork/patch/17776
Submitter: Gregory Etelson <gregory@weka.io>
Date: Fri, 09 Dec 2016 10:54:39 +0200
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:755c78f7b493983eb318b5aa2635a38f6e4c694d
Repo:dpdk-next-net, Branch:master, CommitID:00c87c6695a0217c32e654c221bda3d1d2e21c3d
Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
Repo:dpdk, Branch:master, CommitID:c431384c8fbf8503693bcae1bdcd58d6fa459b8a
Apply patch file failed:
Repo: dpdk-next-crypto
17776:
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 170 with fuzz 1.
Hunk #2 FAILED at 378.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
can't find file to patch at input line 63
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|
|
|
|
|
|diff --git a/src/ixgbevf_main.c b/src/ixgbevf_main.c
|index c5a922f..b96d9f0 100644
|--- a/src/ixgbevf_main.c
|+++ b/src/ixgbevf_main.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-net
17776:
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 170 with fuzz 1.
Hunk #2 FAILED at 378.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
can't find file to patch at input line 63
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|
|
|
|
|
|diff --git a/src/ixgbevf_main.c b/src/ixgbevf_main.c
|index c5a922f..b96d9f0 100644
|--- a/src/ixgbevf_main.c
|+++ b/src/ixgbevf_main.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-virtio
17776:
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 170 with fuzz 1.
Hunk #2 FAILED at 378.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
can't find file to patch at input line 63
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|
|
|
|
|
|diff --git a/src/ixgbevf_main.c b/src/ixgbevf_main.c
|index c5a922f..b96d9f0 100644
|--- a/src/ixgbevf_main.c
|+++ b/src/ixgbevf_main.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk
17776:
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 170 with fuzz 1.
Hunk #2 FAILED at 378.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
can't find file to patch at input line 63
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|
|
|
|
|
|diff --git a/src/ixgbevf_main.c b/src/ixgbevf_main.c
|index c5a922f..b96d9f0 100644
|--- a/src/ixgbevf_main.c
|+++ b/src/ixgbevf_main.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
DPDK STV team
reply other threads:[~2016-12-09 9:16 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='587443$f2pis@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=gregory@weka.io \
--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).