From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw55499[v3, 14/14] eal: prevent different primary/secondary process versions
Date: 27 Jun 2019 07:07:02 -0700 [thread overview]
Message-ID: <ee68f5$7ae3lb@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/55499
_apply issues_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: 2019-06-27 11:39:09
Reply_mail: a828f9e8c9aa1798fdef50a12ee074d287d00eb5.1561635481.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: da5fa4d4d6d1b1fd82dee4830fa5364d6ac9270f
*Repo: dpdk
#include <rte_eal_memconfig.h>
#include "eal_internal_cfg.h"
#include "eal_memcfg.h"
error: patch failed: lib/librte_eal/common/eal_common_mcfg.c:4
error: lib/librte_eal/common/eal_common_mcfg.c: patch does not apply
Checking patch lib/librte_eal/common/eal_memcfg.h...
error: while searching for:
void
eal_mcfg_wait_complete(void);
/* set mem config as complete */
void
eal_mcfg_complete(void);
error: patch failed: lib/librte_eal/common/eal_memcfg.h:80
error: lib/librte_eal/common/eal_memcfg.h: patch does not apply
Checking patch lib/librte_eal/freebsd/eal/eal.c...
error: while searching for:
if (rte_eal_config_attach() < 0)
return -1;
eal_mcfg_wait_complete();
if (rte_eal_config_reattach() < 0)
return -1;
eal_mcfg_update_from_internal();
error: patch failed: lib/librte_eal/freebsd/eal/eal.c:385
error: lib/librte_eal/freebsd/eal/eal.c: patch does not apply
Checking patch lib/librte_eal/linux/eal/eal.c...
error: while searching for:
if (rte_eal_config_attach() < 0)
return -1;
eal_mcfg_wait_complete();
if (rte_eal_config_reattach() < 0)
return -1;
eal_mcfg_update_internal();
error: patch failed: lib/librte_eal/linux/eal/eal.c:488
error: lib/librte_eal/linux/eal/eal.c: patch does not apply
DPDK STV team
reply other threads:[~2019-06-27 14:07 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='ee68f5$7ae3lb@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).