From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw62675[v7, 07/12] app/test: clean LTO build warnings (maybe-uninitialized)
Date: 10 Nov 2019 09:03:44 -0800 [thread overview]
Message-ID: <ee68f5$8hltnl@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62675
_apply issues_
Submitter: Andrzej Ostruszka <aostruszka@marvell.com>
Date: 2019-11-07 15:03:13
Reply_mail: 20191107150318.3677-8-aostruszka@marvell.com
DPDK git baseline:
Repo:dpdk, CommitID: 6bbc5a9236250b708c6d1931e966c74da381b4f2
*Repo: dpdk
void *data;
rte_hash_lookup_data(tbl_rw_test_param.h,
tbl_rw_test_param.keys + i,
&data);
error: patch failed: app/test/test_hash_readwrite.c:298
error: app/test/test_hash_readwrite.c: patch does not apply
Checking patch app/test/test_link_bonding_mode4.c...
error: while searching for:
{
struct rte_eth_bond_8023ad_conf conf;
--
rte_eth_bond_8023ad_conf_get(test_params.bonded_port_id, &conf);
return conf.update_timeout_ms;
}
error: patch failed: app/test/test_link_bonding_mode4.c:585
error: app/test/test_link_bonding_mode4.c: patch does not apply
Checking patch app/test/test_memzone.c...
error: while searching for:
struct rte_malloc_socket_stats stats;
size_t len, overhead;
--
rte_malloc_get_socket_stats(socket_id, &stats);
len = stats.greatest_free_size;
overhead = MALLOC_ELEM_OVERHEAD;
error: patch failed: app/test/test_memzone.c:475
error: app/test/test_memzone.c: patch does not apply
DPDK STV team
reply other threads:[~2019-11-10 17:03 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$8hltnl@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).