automatic DPDK test reports
 help / color / mirror / Atom feed
* [dpdk-test-report] |FAILURE| pw17776 [PATCH] IGB_UIO: PCI Resources Management
@ 2016-12-09  9:16 sys_stv
  0 siblings, 0 replies; only message in thread
From: sys_stv @ 2016-12-09  9:16 UTC (permalink / raw)
  To: test-report; +Cc: gregory

[-- 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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-12-09  9:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-12-09  9:16 [dpdk-test-report] |FAILURE| pw17776 [PATCH] IGB_UIO: PCI Resources Management sys_stv

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).