From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yuanhan.liu@linux.intel.com
Subject: [dpdk-test-report] |FAILURE| pw23106 [PATCH v4 10/22] vhost: export the number of vrings
Date: 02 Apr 2017 07:57:36 -0700 [thread overview]
Message-ID: <e81775$11ljtth@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3017 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23106
_apply patch file failure_
Submitter: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Date: Sat, 1 Apr 2017 15:22:39 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:40546b9f72d7367f2ee33c8061896e5c0e92f207
Repo:dpdk-next-crypto, Branch:master, CommitID:3989a0933afab9d339ed9c6de258185d30bb7cb5
Repo:dpdk-next-net, Branch:master, CommitID:a962e4db963d57c1c4c48e46716fc5a63a59542f
Repo:dpdk-next-virtio, Branch:master, CommitID:26f5fd077415b94bb4aacd857d38ae25841f4fe7
Repo:dpdk, Branch:master, CommitID:ba82829fda022e14a938c3a669de0e634626e4c8
Apply patch file failed:
Repo: dpdk
23106:
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 succeeded at 188 (offset -20 lines).
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 succeeded at 572 with fuzz 1 (offset 3 lines).
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/rte_vhost_version.map.rej
patching file lib/librte_vhost/rte_virtio_net.h
Hunk #1 succeeded at 226 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 319 (offset 2 lines).
Repo: dpdk-next-crypto
23106:
patching file doc/guides/rel_notes/release_17_05.rst
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 succeeded at 572 with fuzz 1 (offset 3 lines).
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/rte_vhost_version.map.rej
patching file lib/librte_vhost/rte_virtio_net.h
Hunk #1 succeeded at 226 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 319 (offset 2 lines).
Repo: dpdk-next-net
23106:
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 succeeded at 286 (offset 78 lines).
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 succeeded at 598 with fuzz 1 (offset 29 lines).
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/rte_vhost_version.map.rej
patching file lib/librte_vhost/rte_virtio_net.h
Hunk #1 succeeded at 226 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 319 (offset 2 lines).
Repo: dpdk-next-eventdev
23106:
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 succeeded at 213 (offset 5 lines).
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 succeeded at 572 with fuzz 1 (offset 3 lines).
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/rte_vhost_version.map.rej
patching file lib/librte_vhost/rte_virtio_net.h
Hunk #1 succeeded at 226 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 319 (offset 2 lines).
DPDK STV team
reply other threads:[~2017-04-02 14:57 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$11ljtth@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yuanhan.liu@linux.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).