From: Eric Long <i@hack3r.moe>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Eric Long <i@hack3r.moe>
Subject: [PATCH] test: raise fast test timeout to 60s on RISC-V
Date: Sat, 23 Nov 2024 22:58:10 +0800 [thread overview]
Message-ID: <MW4PR11MB8289B816B08C6E19716B8F82D72C2@MW4PR11MB8289.namprd11.prod.outlook.com> (raw)
Current RISC-V hardware (e.g. HiFive Unmatched) is still way too slow
compared to other architectures' counterparts. On the most powerful
RISC-V CPU available (SG2042), DPDK still fails with 4 timeouts:
```
Summary of Failures:
23/77 DPDK:fast-tests / eventdev_selftest_sw TIMEOUT
10.06s killed by signal 15 SIGTERM
56/77 DPDK:fast-tests / rib6_autotest TIMEOUT
10.04s
64/77 DPDK:fast-tests / spinlock_autotest TIMEOUT
10.06s killed by signal 15 SIGTERM
66/77 DPDK:fast-tests / table_autotest TIMEOUT
11.28s killed by signal 15 SIGTERM
```
On HiFive Unmatched, the longest test takes 53 seconds:
```
37/77 DPDK:fast-tests / lpm6_autotest OK
53.29s
```
Raising timeout to 60s on RISC-V target will help test effectiveness
on it.
Signed-off-by: Eric Long <i@hack3r.moe>
---
.mailmap | 1 +
app/test/suites/meson.build | 5 +++++
2 files changed, 6 insertions(+)
diff --git a/.mailmap b/.mailmap
index 7334ad58a9..24f3f4a0cd 100644
--- a/.mailmap
+++ b/.mailmap
@@ -404,6 +404,7 @@ Erez Ferber <erezf@nvidia.com> <erezf@mellanox.com>
Erez Shitrit <erezsh@nvidia.com>
Eric Joyner <eric.joyner@intel.com>
Eric Kinzie <ekinzie@brocade.com> <ehkinzie@gmail.com>
+Eric Long <i@hack3r.moe>
Eric Zhang <eric.zhang@windriver.com>
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Erik Ziegenbalg <eziegenb@brocade.com>
diff --git a/app/test/suites/meson.build b/app/test/suites/meson.build
index 191702cf76..b74d1c4ad7 100644
--- a/app/test/suites/meson.build
+++ b/app/test/suites/meson.build
@@ -6,6 +6,11 @@
timeout_seconds = 600
timeout_seconds_fast = 10
+if arch_subdir == 'riscv'
+ # Current RISC-V machines are too slow to finish fast tests under 10s
+ timeout_seconds_fast = 60
+endif
+
test_no_huge_args = ['--no-huge', '-m', '2048']
has_hugepage = run_command(has_hugepages_cmd, check: true).stdout().strip() != '0'
message('hugepage availability: @0@'.format(has_hugepage))
--
2.47.0
reply other threads:[~2024-11-23 15:00 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=MW4PR11MB8289B816B08C6E19716B8F82D72C2@MW4PR11MB8289.namprd11.prod.outlook.com \
--to=i@hack3r.moe \
--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).