automatic DPDK test reports
 help / color / mirror / Atom feed
* [dpdk-test-report] |FAILURE| pw34106 [PATCH RFC 12/24] vhost: move slave_req_fd field to AF_UNIX transport
@ 2018-01-22  6:12 sys_stv
  0 siblings, 0 replies; only message in thread
From: sys_stv @ 2018-01-22  6:12 UTC (permalink / raw)
  To: test-report; +Cc: stefanha

[-- Attachment #1: Type: text/plain, Size: 5354 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/34106

_apply patch file failure_

Submitter: Stefan Hajnoczi <stefanha@redhat.com>
Date: Fri, 19 Jan 2018 13:44:35 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18daa7305ffd89b443cf56694fd30790cca0d3ce
                   Repo:dpdk-next-crypto, Branch:master, CommitID:a1472935a8b81a328ed8d6f553ee2523fea96757
                   Repo:dpdk-next-net, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
                   Repo:dpdk-next-virtio, Branch:master, CommitID:dd854ceec2e09a93f2509de03ae6d67e201b1a2b
                   Repo:dpdk, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
                   
Apply patch file failed:
Repo: dpdk
34106:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 252.
Hunk #2 FAILED at 290.
Hunk #3 succeeded at 237 with fuzz 1 (offset -94 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_vhost/trans_af_unix.c b/lib/librte_vhost/trans_af_unix.c
|index 9e5a5c127..7128e121e 100644
|--- a/lib/librte_vhost/trans_af_unix.c
|+++ b/lib/librte_vhost/trans_af_unix.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #2 FAILED at 288.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
patching file lib/librte_vhost/vhost_user.c
Hunk #2 succeeded at 1056 (offset 31 lines).

Repo: dpdk-next-crypto
34106:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 252.
Hunk #2 FAILED at 290.
Hunk #3 succeeded at 235 with fuzz 1 (offset -96 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_vhost/trans_af_unix.c b/lib/librte_vhost/trans_af_unix.c
|index 9e5a5c127..7128e121e 100644
|--- a/lib/librte_vhost/trans_af_unix.c
|+++ b/lib/librte_vhost/trans_af_unix.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #2 FAILED at 288.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
patching file lib/librte_vhost/vhost_user.c

Repo: dpdk-next-net
34106:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 252.
Hunk #2 FAILED at 290.
Hunk #3 succeeded at 237 with fuzz 1 (offset -94 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_vhost/trans_af_unix.c b/lib/librte_vhost/trans_af_unix.c
|index 9e5a5c127..7128e121e 100644
|--- a/lib/librte_vhost/trans_af_unix.c
|+++ b/lib/librte_vhost/trans_af_unix.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #2 FAILED at 288.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
patching file lib/librte_vhost/vhost_user.c
Hunk #2 succeeded at 1056 (offset 31 lines).

Repo: dpdk-next-virtio
34106:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 252.
Hunk #2 FAILED at 290.
Hunk #3 succeeded at 237 with fuzz 1 (offset -94 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_vhost/trans_af_unix.c b/lib/librte_vhost/trans_af_unix.c
|index 9e5a5c127..7128e121e 100644
|--- a/lib/librte_vhost/trans_af_unix.c
|+++ b/lib/librte_vhost/trans_af_unix.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #2 FAILED at 288.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
patching file lib/librte_vhost/vhost_user.c
Hunk #2 succeeded at 1056 (offset 31 lines).

Repo: dpdk-next-eventdev
34106:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 252.
Hunk #2 FAILED at 290.
Hunk #3 succeeded at 235 with fuzz 1 (offset -96 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_vhost/trans_af_unix.c b/lib/librte_vhost/trans_af_unix.c
|index 9e5a5c127..7128e121e 100644
|--- a/lib/librte_vhost/trans_af_unix.c
|+++ b/lib/librte_vhost/trans_af_unix.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #2 FAILED at 288.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
patching file lib/librte_vhost/vhost_user.c


DPDK STV team

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

only message in thread, other threads:[~2018-01-22  6:12 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-22  6:12 [dpdk-test-report] |FAILURE| pw34106 [PATCH RFC 12/24] vhost: move slave_req_fd field to AF_UNIX transport 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).