From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(71523) [v9, 04/12] eal/mem: extract common code for memseg list initialization
Date: 16 Jun 2020 20:26:35 -0700 [thread overview]
Message-ID: <fecc85$afkf9u@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/71523
_apply issues_
Submitter: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Date: 2020-06-15 00:43:46
Reply_mail: 20200615004354.14380-5-dmitry.kozliuk@gmail.com
DPDK git baseline:
Repo:dpdk, CommitID: 0371535d46c91ddc7a127e3a294a6c040bd5c763
* Repo: dpdk
/*
error: patch failed: lib/librte_eal/common/eal_common_memory.c:25
error: lib/librte_eal/common/eal_common_memory.c: patch does not apply
Checking patch lib/librte_eal/common/eal_private.h...
error: while searching for:
--
* Get cpu core_id.
*
error: patch failed: lib/librte_eal/common/eal_private.h:254
error: lib/librte_eal/common/eal_private.h: patch does not apply
Checking patch lib/librte_eal/freebsd/eal_memory.c...
error: while searching for:
--
addr = mmap(NULL, internal_config.memory,
PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
if (addr == MAP_FAILED) {
RTE_LOG(ERR, EAL, "%s: mmap() failed: %s\n", __func__,
strerror(errno));
return -1;
}
--
}
error: patch failed: lib/librte_eal/freebsd/eal_memory.c:64
error: lib/librte_eal/freebsd/eal_memory.c: patch does not apply
Checking patch lib/librte_eal/linux/eal_memory.c...
error: while searching for:
--
if (rte_fbarray_destroy(&msl->memseg_arr)) {
RTE_LOG(ERR, EAL, "Cannot destroy memseg list\n");
error: patch failed: lib/librte_eal/linux/eal_memory.c:802
error: lib/librte_eal/linux/eal_memory.c: patch does not apply
DPDK STV team
next reply other threads:[~2020-06-17 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 3:26 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-16 15:32 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$afkf9u@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).