automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw(72242) [v3, 11/14] examples/vdpa: use new wrappers instead of ops
Date: 28 Jun 2020 09:02:46 -0700	[thread overview]
Message-ID: <fecc85$aiovk6@orsmga001.jf.intel.com> (raw)

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


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

_apply issues_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: 2020-06-26 13:27:09
Reply_mail: 20200626132712.1437673-12-maxime.coquelin@redhat.com

DPDK git baseline:
	Repo:dpdk-next-virtio, CommitID: 4a756a8c2f9dbf1f43e2638028931331e2a617eb
	Repo:dpdk, CommitID: 6248368a9ae1eadf6b7fb05ab37497afdb714429


* Repo: dpdk-next-virtio
continue;
		if (vdev->ops->get_queue_num(vdev, &queue_num) < 0) {
			RTE_LOG(ERR, VDPA,
				"failed to get vdpa queue number "
				"for device %s.\n", dev->name);
			continue;
		}
		if (vdev->ops->get_features(vdev, &features) < 0) {
			RTE_LOG(ERR, VDPA,
				"failed to get vdpa features "
				"for device %s.\n", dev->name);

error: patch failed: examples/vdpa/main.c:301
error: examples/vdpa/main.c: patch does not apply

* Repo: dpdk
continue;
		if (vdev->ops->get_queue_num(vdev, &queue_num) < 0) {
			RTE_LOG(ERR, VDPA,
				"failed to get vdpa queue number "
				"for device %s.\n", dev->name);
			continue;
		}
		if (vdev->ops->get_features(vdev, &features) < 0) {
			RTE_LOG(ERR, VDPA,
				"failed to get vdpa features "
				"for device %s.\n", dev->name);

error: patch failed: examples/vdpa/main.c:301
error: examples/vdpa/main.c: patch does not apply
DPDK STV team

             reply	other threads:[~2020-06-28 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 16:02 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-26 18:40 sys_stv

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='fecc85$aiovk6@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.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).