automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw35663[dpdk-dev] vhost: stop device before updating public vring data
Date: 21 May 2018 19:34:10 -0700	[thread overview]
Message-ID: <0590c7$1n7ek2@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Date: 2018-03-05 16:11:08
DPDK git baseline:
	Repo:dpdk-master, CommitID: fe613657ce486083a3ed96890c95de4f35c8593b
	Repo:dpdk-next-eventdev, CommitID: 3c955492b601d65402c02ac81dfdc7eeb62f23c9
	Repo:dpdk-next-net, CommitID: db1a11e519444772a18f50bef5ded66e1d43cae2
	Repo:dpdk-next-crypto, CommitID: a7ac03988bb2c64ad9c58970f0b9fd582e791058
	Repo:dpdk-next-virtio, CommitID: 317fe244a65ea2a5753e839f7d094b3d8677fac6

*Repo: dpdk-master
Hunk #2 succeeded at 560 (offset 69 lines).
Hunk #3 succeeded at 596 (offset 69 lines).
Hunk #4 succeeded at 936 (offset 124 lines).
Hunk #5 succeeded at 964 (offset 124 lines).
Hunk #6 succeeded at 1132 (offset 145 lines).
error: while searching for:
		return -1;
	}

	size = msg->payload.log.mmap_size;
	off  = msg->payload.log.mmap_offset;
	RTE_LOG(INFO, VHOST_CONFIG,

error: patch failed: lib/librte_vhost/vhost_user.c:981
error: lib/librte_vhost/vhost_user.c: patch does not apply
*Repo: dpdk-next-eventdev
Hunk #2 succeeded at 560 (offset 69 lines).
Hunk #3 succeeded at 596 (offset 69 lines).
Hunk #4 succeeded at 916 (offset 104 lines).
Hunk #5 succeeded at 944 (offset 104 lines).
Hunk #6 succeeded at 1112 (offset 125 lines).
error: while searching for:
		return -1;
	}

	size = msg->payload.log.mmap_size;
	off  = msg->payload.log.mmap_offset;
	RTE_LOG(INFO, VHOST_CONFIG,

error: patch failed: lib/librte_vhost/vhost_user.c:981
error: lib/librte_vhost/vhost_user.c: patch does not apply
*Repo: dpdk-next-net
Hunk #2 succeeded at 560 (offset 69 lines).
Hunk #3 succeeded at 596 (offset 69 lines).
Hunk #4 succeeded at 936 (offset 124 lines).
Hunk #5 succeeded at 964 (offset 124 lines).
Hunk #6 succeeded at 1132 (offset 145 lines).
error: while searching for:
		return -1;
	}

	size = msg->payload.log.mmap_size;
	off  = msg->payload.log.mmap_offset;
	RTE_LOG(INFO, VHOST_CONFIG,

error: patch failed: lib/librte_vhost/vhost_user.c:981
error: lib/librte_vhost/vhost_user.c: patch does not apply
*Repo: dpdk-next-crypto
Hunk #2 succeeded at 560 (offset 69 lines).
Hunk #3 succeeded at 596 (offset 69 lines).
Hunk #4 succeeded at 936 (offset 124 lines).
Hunk #5 succeeded at 964 (offset 124 lines).
Hunk #6 succeeded at 1132 (offset 145 lines).
error: while searching for:
		return -1;
	}

	size = msg->payload.log.mmap_size;
	off  = msg->payload.log.mmap_offset;
	RTE_LOG(INFO, VHOST_CONFIG,

error: patch failed: lib/librte_vhost/vhost_user.c:981
error: lib/librte_vhost/vhost_user.c: patch does not apply
*Repo: dpdk-next-virtio
Hunk #2 succeeded at 560 (offset 69 lines).
Hunk #3 succeeded at 596 (offset 69 lines).
Hunk #4 succeeded at 936 (offset 124 lines).
Hunk #5 succeeded at 964 (offset 124 lines).
Hunk #6 succeeded at 1132 (offset 145 lines).
error: while searching for:
		return -1;
	}

	size = msg->payload.log.mmap_size;
	off  = msg->payload.log.mmap_offset;
	RTE_LOG(INFO, VHOST_CONFIG,

error: patch failed: lib/librte_vhost/vhost_user.c:981
error: lib/librte_vhost/vhost_user.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2018-05-22  2:34 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='0590c7$1n7ek2@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=peipeix.lu@intel.com \
    --cc=test-report@dpdk.org \
    --cc=xinfengx.zhao@intel.com \
    --cc=zhaoyan.chen@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).