From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yu.y.liu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw26851 [PATCH] vhost: fix vhost-user init failed
Date: 14 Jul 2017 00:35:47 -0700 [thread overview]
Message-ID: <e81775$12u4nfg@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26851
_apply patch file failure_
Submitter: "Liu, Yu Y" <yu.y.liu@intel.com>
Date: Wed, 12 Jul 2017 02:41:09 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:76ee670f6a91f27eed7e06d2272db68f527c2a8b
Repo:dpdk-next-crypto, Branch:master, CommitID:d25e609a593c356edb47d2be2dd5fef27518f0b6
Repo:dpdk-next-net, Branch:master, CommitID:b3d4e665ed3db9fb21ba016a28294245d578e012
Repo:dpdk-next-virtio, Branch:master, CommitID:42003749105c3bbd7a9e2664263d89e502665cbe
Repo:dpdk, Branch:master, CommitID:7ee3e9446290ba3f618d8cb93374e76994057057
Apply patch file failed:
Repo: dpdk
26851:
patching file lib/librte_vhost/socket.c
Hunk #1 FAILED at 668.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-crypto
26851:
patching file lib/librte_vhost/socket.c
Hunk #1 FAILED at 668.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-net
26851:
patching file lib/librte_vhost/socket.c
Hunk #1 FAILED at 668.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-virtio
26851:
patching file lib/librte_vhost/socket.c
Hunk #1 FAILED at 668.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-eventdev
26851:
patching file lib/librte_vhost/socket.c
Hunk #1 FAILED at 668.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
DPDK STV team
reply other threads:[~2017-07-14 7:35 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='e81775$12u4nfg@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yu.y.liu@intel.com \
/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).