From: <agupta3@marvell.com>
Cc: <dev@dpdk.org>, Amit Gupta <agupta3@marvell.com>
Subject: [dpdk-dev] [PATCH] test/meson: hash lf test moved to dpdk perf testsuite
Date: Thu, 5 Sep 2019 21:24:43 +0530 [thread overview]
Message-ID: <1567698883-10307-1-git-send-email-agupta3@marvell.com> (raw)
From: Amit Gupta <agupta3@marvell.com>
hash_readwrite_lf test always getting TIMEOUT as required
time to finish this test was much longer compare to time
required for fast tests(10s). Hence, the test is being moved to
perf test category for execution to complete.
Change-Id: I64ae14a5ecfbea466d8a057c070579c0794a7377
Signed-off-by: Amit Gupta <agupta3@marvell.com>
---
app/test/meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/meson.build b/app/test/meson.build
index 94fd9f8..34141c5 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -220,7 +220,6 @@ fast_test_names = [
'eventdev_common_autotest',
'fbarray_autotest',
'hash_readwrite_func_autotest',
- 'hash_readwrite_lf_autotest',
'ipsec_autotest',
'kni_autotest',
'kvargs_autotest',
@@ -263,6 +262,7 @@ perf_test_names = [
'stack_lf_perf_autotest',
'rand_perf_autotest',
'hash_readwrite_perf_autotest',
+ 'hash_readwrite_lf_autotest',
]
driver_test_names = [
--
1.8.3.1
reply other threads:[~2019-09-05 15:54 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=1567698883-10307-1-git-send-email-agupta3@marvell.com \
--to=agupta3@marvell.com \
--cc=dev@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).