automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: santosh.shukla@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw25194 [PATCH 06/10] bsdapp/eal: detect iova mapping mode
Date: 12 Jun 2017 05:04:49 -0700	[thread overview]
Message-ID: <e81775$12hmr7p@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Date: Thu,  8 Jun 2017 16:35:09 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:a93a816c27484017b86af9d19566218a846251f1
                   Repo:dpdk-next-crypto, Branch:master, CommitID:b1cac453935eb8d2f1dee8e7ab081711cfb0cf70
                   Repo:dpdk-next-net, Branch:master, CommitID:6a4d050e285599451fa481a6063d4d66c3758982
                   Repo:dpdk-next-virtio, Branch:master, CommitID:101a00a4811479e7f66829e523c9138288831b39
                   Repo:dpdk, Branch:master, CommitID:a6793d47f328354d0a3a3984060bbfb967e4f91d
                   
Apply patch file failed:
Repo: dpdk
25194:
patching file lib/librte_eal/bsdapp/eal/eal.c
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 199.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej

Repo: dpdk-next-crypto
25194:
patching file lib/librte_eal/bsdapp/eal/eal.c
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 199.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej

Repo: dpdk-next-net
25194:
patching file lib/librte_eal/bsdapp/eal/eal.c
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 199.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej

Repo: dpdk-next-virtio
25194:
patching file lib/librte_eal/bsdapp/eal/eal.c
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 199.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej

Repo: dpdk-next-eventdev
25194:
patching file lib/librte_eal/bsdapp/eal/eal.c
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 199.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej


DPDK STV team

                 reply	other threads:[~2017-06-12 12:04 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$12hmr7p@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=santosh.shukla@caviumnetworks.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).