From: luca.boccassi@gmail.com
To: dev@dpdk.org
Subject: [PATCH] test: move lcores/pdump/pflock/ticketlock out of fast suite
Date: Fri, 12 Jan 2024 20:10:56 +0000 [thread overview]
Message-ID: <20240112201056.452598-1-luca.boccassi@gmail.com> (raw)
From: Luca Boccassi <bluca@debian.org>
These tests are failing with timeouts on build machines with large amount
of cores, so move them out of the fast suite, which should complete in seconds.
33/77 DPDK:fast-tests / lcores_autotest TIMEOUT 50.01s
https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_11/aarch64
43/77 DPDK:fast-tests / pdump_autotest TIMEOUT 120.11s killed by signal 15 SIGTERM
https://ci.debian.net/packages/d/dpdk/unstable/ppc64el/41544027/#S10
45/77 DPDK:fast-tests / pflock_autotest TIMEOUT 120.14s killed by signal 15 SIGTERM
72/77 DPDK:fast-tests / ticketlock_autotest TIMEOUT 120.12s killed by signal 15 SIGTERM
https://ci.debian.net/packages/d/dpdk/unstable/amd64/41560884/#S10
Signed-off-by: Luca Boccassi <bluca@debian.org>
---
app/test/test_lcores.c | 2 +-
app/test/test_pdump.c | 2 +-
app/test/test_pflock.c | 2 +-
app/test/test_ticketlock.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/app/test/test_lcores.c b/app/test/test_lcores.c
index 22225a9fd3..bebd830399 100644
--- a/app/test/test_lcores.c
+++ b/app/test/test_lcores.c
@@ -411,4 +411,4 @@ test_lcores(void)
return TEST_SUCCESS;
}
-REGISTER_FAST_TEST(lcores_autotest, true, true, test_lcores);
+REGISTER_TEST_COMMAND(lcores_autotest, test_lcores);
diff --git a/app/test/test_pdump.c b/app/test/test_pdump.c
index 9f7769707e..adf49f0b54 100644
--- a/app/test/test_pdump.c
+++ b/app/test/test_pdump.c
@@ -219,4 +219,4 @@ test_pdump(void)
return TEST_SUCCESS;
}
-REGISTER_FAST_TEST(pdump_autotest, true, false, test_pdump);
+REGISTER_TEST_COMMAND(pdump_autotest, test_pdump);
diff --git a/app/test/test_pflock.c b/app/test/test_pflock.c
index 5f77b158c8..38da6bce27 100644
--- a/app/test/test_pflock.c
+++ b/app/test/test_pflock.c
@@ -193,4 +193,4 @@ test_pflock(void)
return 0;
}
-REGISTER_FAST_TEST(pflock_autotest, true, true, test_pflock);
+REGISTER_TEST_COMMAND(pflock_autotest, test_pflock);
diff --git a/app/test/test_ticketlock.c b/app/test/test_ticketlock.c
index 1fbbedb33b..242c136478 100644
--- a/app/test/test_ticketlock.c
+++ b/app/test/test_ticketlock.c
@@ -314,4 +314,4 @@ test_ticketlock(void)
return ret;
}
-REGISTER_FAST_TEST(ticketlock_autotest, true, true, test_ticketlock);
+REGISTER_TEST_COMMAND(ticketlock_autotest, test_ticketlock);
--
2.39.2
reply other threads:[~2024-01-12 20:11 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=20240112201056.452598-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.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).