automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw23527 [PATCH v2 02/42] eal: parse "driver" device argument before probing drivers
Date: 12 Apr 2017 07:19:39 -0700	[thread overview]
Message-ID: <e624e2$11apmah@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Tue, 11 Apr 2017 17:44:09 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
                   Repo:dpdk-next-crypto, Branch:master, CommitID:41c63e15eb931fee8e52e36570cab79a9817b960
                   Repo:dpdk-next-net, Branch:master, CommitID:0dda07fc09ea3b96fe997c2b4243ef48c619cc22
                   Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
                   Repo:dpdk, Branch:master, CommitID:4b6fa6d32d2acfce5960522ba904929ee5274eb7
                   
Apply patch file failed:
Repo: dpdk
23527:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 72.
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 105.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-crypto
23527:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 72.
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 105.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-net
23527:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 72.
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 105.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-virtio
23527:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 72.
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 105.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-eventdev
23527:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 72.
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 105.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej


DPDK STV team

                 reply	other threads:[~2017-04-12 14:19 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='e624e2$11apmah@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=gaetan.rivet@6wind.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).