From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw62537[1/2] test/rib: speed up rib autotests
Date: 08 Nov 2019 08:01:11 -0800 [thread overview]
Message-ID: <ee68f5$8h85dc@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62537
_apply issues_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: 2019-11-06 12:21:46
Reply_mail: dd22d4d965e4e932a7e3408ea889dc3fe2892cce.1573042633.git.vladimir.medvedkin@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 9a643edb2b74c5993465089aa23178cd9ad612cc
*Repo: dpdk
'lpm_perf_autotest',
'fib_slow_autotest',
'fib_perf_autotest',
'red_all',
error: patch failed: app/test/meson.build:259
error: app/test/meson.build: patch does not apply
Checking patch app/test/test_rib.c...
error: while searching for:
config.ext_sz = 0;
--
for (i = 0; i < 10; i++) {
config.max_nodes = MAX_RULES - i;
rib = rte_rib_create(__func__, SOCKET_ID_ANY, &config);
RTE_TEST_ASSERT(rib != NULL, "Failed to create RIB\n");
error: patch failed: app/test/test_rib.c:76
error: app/test/test_rib.c: patch does not apply
DPDK STV team
reply other threads:[~2019-11-08 16:01 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$8h85dc@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).