automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yuanhan.liu@linux.intel.com
Subject: [dpdk-test-report] |FAILURE| pw22603 [PATCH v3 07/22] vhost: export vhost vring info
Date: 29 Mar 2017 02:22:46 -0700	[thread overview]
Message-ID: <e81775$11k4b4b@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Date: Tue, 28 Mar 2017 20:45:42 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
                   Repo:dpdk-next-crypto, Branch:master, CommitID:3eacd5a3ef2aa2f811b943659560c37fbd332b84
                   Repo:dpdk-next-net, Branch:master, CommitID:c2d500f4c334fe59bb48709f99b9febe75bbad0d
                   Repo:dpdk-next-virtio, Branch:master, CommitID:8ec4aa31199c361151610ef54427d5f91c3dac8c
                   Repo:dpdk, Branch:master, CommitID:b88161be422750fca0e66c76385d3d00912ba8fb
                   
Apply patch file failed:
Repo: dpdk
22603:
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 38.
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 #2 succeeded at 288 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 396 (offset 2 lines).
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 120.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej

Repo: dpdk-next-crypto
22603:
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 38.
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 #2 succeeded at 288 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 396 (offset 2 lines).
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 120.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej

Repo: dpdk-next-net
22603:
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 38.
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 #2 succeeded at 288 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 396 (offset 2 lines).
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 120.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej

Repo: dpdk-next-eventdev
22603:
patching file lib/librte_vhost/rte_vhost_version.map
Hunk #1 FAILED at 38.
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 #2 succeeded at 288 (offset -15 lines).
patching file lib/librte_vhost/vhost.c
Hunk #1 succeeded at 396 (offset 2 lines).
patching file lib/librte_vhost/vhost.h
Hunk #1 FAILED at 120.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.h.rej


DPDK STV team

                 reply	other threads:[~2017-03-29  9:22 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$11k4b4b@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).