From: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, aconole@redhat.com, david.marchand@redhat.com
Subject: [dpdk-dev] [PATCH 1/2] test/rib: speed up rib autotests
Date: Wed, 6 Nov 2019 12:21:46 +0000 [thread overview]
Message-ID: <dd22d4d965e4e932a7e3408ea889dc3fe2892cce.1573042633.git.vladimir.medvedkin@intel.com> (raw)
Split slow part of rib_autotest into rib_slow_autotest
Fixes: b35df4dd666e ("test/rib: add autotests")
Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
---
app/test/autotest_data.py | 6 ++++++
app/test/meson.build | 1 +
app/test/test_rib.c | 20 ++++++++++++++++++--
3 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/app/test/autotest_data.py b/app/test/autotest_data.py
index e89707e..ab150db 100644
--- a/app/test/autotest_data.py
+++ b/app/test/autotest_data.py
@@ -117,6 +117,12 @@
"Report": None,
},
{
+ "Name": "RIB slow autotest",
+ "Command": "rib_slow_autotest",
+ "Func": default_autotest,
+ "Report": None,
+ },
+ {
"Name": "RIB6 autotest",
"Command": "rib6_autotest",
"Func": default_autotest,
diff --git a/app/test/meson.build b/app/test/meson.build
index 37ab9d2..8847d5a 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -259,6 +259,7 @@ perf_test_names = [
'reciprocal_division',
'reciprocal_division_perf',
'lpm_perf_autotest',
+ 'rib_slow_autotest',
'fib_slow_autotest',
'fib_perf_autotest',
'red_all',
diff --git a/app/test/test_rib.c b/app/test/test_rib.c
index c95957a..3dc48fe 100644
--- a/app/test/test_rib.c
+++ b/app/test/test_rib.c
@@ -76,7 +76,7 @@ test_multiple_create(void)
config.ext_sz = 0;
- for (i = 0; i < 10; i++) {
+ for (i = 0; i < 100; 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");
@@ -329,7 +329,6 @@ static struct unit_test_suite rib_tests = {
.teardown = NULL,
.unit_test_cases = {
TEST_CASE(test_create_invalid),
- TEST_CASE(test_multiple_create),
TEST_CASE(test_free_null),
TEST_CASE(test_insert_invalid),
TEST_CASE(test_get_fn),
@@ -339,6 +338,16 @@ static struct unit_test_suite rib_tests = {
}
};
+static struct unit_test_suite rib_slow_tests = {
+ .suite_name = "rib slow autotest",
+ .setup = NULL,
+ .teardown = NULL,
+ .unit_test_cases = {
+ TEST_CASE(test_multiple_create),
+ TEST_CASES_END()
+ }
+};
+
/*
* Do all unit tests.
*/
@@ -348,4 +357,11 @@ test_rib(void)
return unit_test_suite_runner(&rib_tests);
}
+static int
+test_slow_rib(void)
+{
+ return unit_test_suite_runner(&rib_slow_tests);
+}
+
REGISTER_TEST_COMMAND(rib_autotest, test_rib);
+REGISTER_TEST_COMMAND(rib_slow_autotest, test_slow_rib);
--
2.7.4
next reply other threads:[~2019-11-06 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:21 Vladimir Medvedkin [this message]
2019-11-06 12:21 ` [dpdk-dev] [PATCH 2/2] test/rib: speed up rib6 autotests Vladimir Medvedkin
2019-11-07 15:22 ` Aaron Conole
2019-11-07 15:21 ` [dpdk-dev] [PATCH 1/2] test/rib: speed up rib autotests Aaron Conole
2019-11-07 16:42 ` David Marchand
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=dd22d4d965e4e932a7e3408ea889dc3fe2892cce.1573042633.git.vladimir.medvedkin@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).