automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw56158[v4, 3/8] eal: add new API to lock/unlock mempool list
Date: 08 Jul 2019 01:32:24 -0700	[thread overview]
Message-ID: <ee68f5$7d77ct@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2019-07-05 13:10:29
Reply_mail: 0c24b8e90a79ec20daca5dfac0130c962d8b1734.1562332112.git.anatoly.burakov@intel.com
DPDK git baseline:
	Repo:dpdk, CommitID: 7ddd2e81697bfc04eafac35082c4e3271721a780

*Repo: dpdk

error: while searching for:
	struct rte_mem_config *mcfg = rte_eal_get_configuration()->mem_config;
	rte_rwlock_write_unlock(&mcfg->qlock);
}

error: patch failed: lib/librte_eal/common/eal_common_mcfg.c:60
error: lib/librte_eal/common/eal_common_mcfg.c: patch does not apply
Checking patch lib/librte_eal/common/include/rte_eal.h...
error: while searching for:
rte_usage_hook_t
rte_set_application_usage_hook(rte_usage_hook_t usage_func);
--

/**
 * Whether EAL is using huge pages (disabled by --no-huge option).
 * The no-huge mode cannot be used with UIO poll-mode drivers like igb/ixgbe.

error: patch failed: lib/librte_eal/common/include/rte_eal.h:446
error: lib/librte_eal/common/include/rte_eal.h: patch does not apply
Checking patch lib/librte_eal/common/include/rte_eal_memconfig.h...
error: while searching for:
void
rte_mcfg_tailq_write_unlock(void);

#ifdef __cplusplus
}
#endif

error: patch failed: lib/librte_eal/common/include/rte_eal_memconfig.h:148
error: lib/librte_eal/common/include/rte_eal_memconfig.h: patch does not apply
Checking patch lib/librte_eal/rte_eal_version.map...
error: while searching for:
	rte_mcfg_mem_read_unlock;
	rte_mcfg_mem_write_lock;
	rte_mcfg_mem_write_unlock;
	rte_mcfg_tailq_read_lock;
	rte_mcfg_tailq_read_unlock;
	rte_mcfg_tailq_write_lock;

error: patch failed: lib/librte_eal/rte_eal_version.map:296
error: lib/librte_eal/rte_eal_version.map: patch does not apply
Checking patch lib/librte_mempool/rte_mempool.c...
error: while searching for:
		return NULL;
	}
--
	rte_rwlock_write_lock(RTE_EAL_MEMPOOL_RWLOCK);

	/*
	 * reserve a memory zone for this mempool: private data is

error: patch failed: lib/librte_mempool/rte_mempool.c:830
error: lib/librte_mempool/rte_mempool.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2019-07-08  8:32 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$7d77ct@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).