From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65500[v2, 4/5] test/hash: move reader writer lock free tests to perf tests
Date: 18 Feb 2020 15:05:15 -0800 [thread overview]
Message-ID: <ee68f5$9cje3j@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65500
_apply issues_
Submitter: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Date: 2020-02-03 19:49:11
Reply_mail: 20200203194912.4669-5-honnappa.nagarahalli@arm.com
DPDK git baseline:
Repo:dpdk, CommitID: e6c78e736d776ba15aa040f5d6a29e43a9147c0b
*Repo: dpdk
SRCS-$(CONFIG_RTE_LIBRTE_HASH) += test_hash_readwrite_lf.c
SRCS-$(CONFIG_RTE_LIBRTE_RIB) += test_rib.c
SRCS-$(CONFIG_RTE_LIBRTE_RIB) += test_rib6.c
error: patch failed: app/test/Makefile:122
error: app/test/Makefile: patch does not apply
Checking patch app/test/autotest_data.py...
error: while searching for:
"Report": None,
},
--
"Command": "hash_readwrite_lf_autotest",
"Func": default_autotest,
"Report": None,
},
error: patch failed: app/test/autotest_data.py:676
error: app/test/autotest_data.py: patch does not apply
Checking patch app/test/meson.build...
error: while searching for:
'test_hash_multiwriter.c',
'test_hash_readwrite.c',
--
'test_hash_readwrite_lf.c',
'test_interrupts.c',
'test_ipsec.c',
'test_ipsec_sad.c',
error: patch failed: app/test/meson.build:59
error: app/test/meson.build: patch does not apply
Checking patch app/test/test_hash_readwrite_lf.c => app/test/test_hash_readwrite_lf_perf.c...
error: app/test/test_hash_readwrite_lf.c: No such file or directory
DPDK STV team
reply other threads:[~2020-02-18 23:05 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$9cje3j@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).