automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37583 [PATCH v4 40/70] eal: add virt2memseg function
Date: 19 Apr 2018 15:17:01 -0700	[thread overview]
Message-ID: <ca5293$1e42vq@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Sun,  8 Apr 2018 21:17:38 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
                   Repo:dpdk-next-crypto, Branch:master, CommitID:8fcc9656bc96eb167676bee48c3d414255f7b593
                   Repo:dpdk-next-net, Branch:master, CommitID:df715f59f164a5c0db5bb1eaab441688ac0d0d0d
                   Repo:dpdk-next-virtio, Branch:master, CommitID:8adbe7e4847060d091c46abcbecd3dfea8362b7a
                   Repo:dpdk, Branch:master, CommitID:34345a9b69bbf5ccd74a3a75cf3cf102a735546a
                   
Apply patch file failed:
Repo: dpdk
37583:
patching file lib/librte_eal/common/eal_common_memory.c
Hunk #1 succeeded at 171 with fuzz 2 (offset 10 lines).
patching file lib/librte_eal/common/include/rte_memory.h
Hunk #1 succeeded at 189 (offset 46 lines).
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 224.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-crypto
37583:
patching file lib/librte_eal/common/eal_common_memory.c
Hunk #1 succeeded at 171 with fuzz 2 (offset 10 lines).
patching file lib/librte_eal/common/include/rte_memory.h
Hunk #1 succeeded at 189 (offset 46 lines).
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 224.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-net
37583:
patching file lib/librte_eal/common/eal_common_memory.c
Hunk #1 succeeded at 171 with fuzz 2 (offset 10 lines).
patching file lib/librte_eal/common/include/rte_memory.h
Hunk #1 succeeded at 189 (offset 46 lines).
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 224.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-virtio
37583:
patching file lib/librte_eal/common/eal_common_memory.c
Hunk #1 succeeded at 171 with fuzz 2 (offset 10 lines).
patching file lib/librte_eal/common/include/rte_memory.h
Hunk #1 succeeded at 189 (offset 46 lines).
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 224.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-eventdev
37583:
patching file lib/librte_eal/common/eal_common_memory.c
Hunk #1 succeeded at 171 with fuzz 2 (offset 10 lines).
patching file lib/librte_eal/common/include/rte_memory.h
Hunk #1 succeeded at 189 (offset 46 lines).
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 224.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej


DPDK STV team

                 reply	other threads:[~2018-04-19 22:17 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='ca5293$1e42vq@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=anatoly.burakov@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).