From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: stefanha@redhat.com
Subject: [dpdk-test-report] |FAILURE| pw34104 [PATCH RFC 10/24] vhost: embed struct virtio_net inside struct vhost_user_connection
Date: 21 Jan 2018 22:36:01 -0800 [thread overview]
Message-ID: <f7a79a$r1doh@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5017 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/34104
_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
34104:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 205 (offset -64 lines).
Hunk #3 succeeded at 345 (offset -94 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 41
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 c85a162e8..dde3e76cd 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.
8 out of 8 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 261 (offset 1 line).
Hunk #2 succeeded at 282 (offset 1 line).
Hunk #3 succeeded at 289 with fuzz 2.
Repo: dpdk-next-crypto
34104:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 203 (offset -66 lines).
Hunk #3 succeeded at 343 (offset -96 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 41
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 c85a162e8..dde3e76cd 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.
8 out of 8 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #3 succeeded at 288 with fuzz 2 (offset -1 lines).
Repo: dpdk-next-net
34104:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 205 (offset -64 lines).
Hunk #3 succeeded at 345 (offset -94 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 41
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 c85a162e8..dde3e76cd 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.
8 out of 8 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 261 (offset 1 line).
Hunk #2 succeeded at 282 (offset 1 line).
Hunk #3 succeeded at 289 with fuzz 2.
Repo: dpdk-next-virtio
34104:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 205 (offset -64 lines).
Hunk #3 succeeded at 345 (offset -94 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 41
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 c85a162e8..dde3e76cd 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.
8 out of 8 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 261 (offset 1 line).
Hunk #2 succeeded at 282 (offset 1 line).
Hunk #3 succeeded at 289 with fuzz 2.
Repo: dpdk-next-eventdev
34104:
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 203 (offset -66 lines).
Hunk #3 succeeded at 343 (offset -96 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej
can't find file to patch at input line 41
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 c85a162e8..dde3e76cd 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.
8 out of 8 hunks ignored
patching file lib/librte_vhost/vhost.c
Hunk #3 succeeded at 288 with fuzz 2 (offset -1 lines).
DPDK STV team
reply other threads:[~2018-01-22 6:36 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='f7a79a$r1doh@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=stefanha@redhat.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).