From: Phil Yang <phil.yang@arm.com>
To: david.marchand@redhat.com, dev@dpdk.org
Cc: aconole@redhat.com, Honnappa.Nagarahalli@arm.com,
Ruifeng.Wang@arm.com, nd@arm.com
Subject: [dpdk-dev] [PATCH v2] test/atomic: reduce the number of loops to avoid timeouts
Date: Tue, 28 Jul 2020 11:41:37 +0800 [thread overview]
Message-ID: <1595907697-20260-1-git-send-email-phil.yang@arm.com> (raw)
In-Reply-To: <1584936978-11899-2-git-send-email-phil.yang@arm.com>
Reduce the number of loops to 10K to avoid the meson test timeout
warning.
For example:
$ sudo meson test -C build --suite DPDK:fast-tests / atomic_autotest -t 50
[...]
1/1 DPDK:fast-tests / atomic_autotest OK 187.35s
Signed-off-by: Phil Yang <phil.yang@arm.com>
---
v2:
Split from the original patchset.
app/test/test_atomic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/test_atomic.c b/app/test/test_atomic.c
index 214452e..9b70f44 100644
--- a/app/test/test_atomic.c
+++ b/app/test/test_atomic.c
@@ -99,7 +99,7 @@
#define NUM_ATOMIC_TYPES 3
-#define N 1000000
+#define N 10000
static rte_atomic16_t a16;
static rte_atomic32_t a32;
--
2.7.4
next prev parent reply other threads:[~2020-07-28 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 4:16 [dpdk-dev] [PATCH 1/2] test/mcslock: move performance test to perf tests Phil Yang
2020-03-23 4:16 ` [dpdk-dev] [PATCH 2/2] test/atomic: reduce the number of loops to avoid timeouts Phil Yang
2020-07-28 3:41 ` Phil Yang [this message]
2020-09-17 9:17 ` [dpdk-dev] [PATCH v2] " Juraj Linkeš
2023-06-13 3:37 ` Stephen Hemminger
2020-07-23 2:36 ` [dpdk-dev] [PATCH 1/2] test/mcslock: move performance test to perf tests Phil Yang
2020-07-23 15:14 ` Aaron Conole
2020-07-28 3:24 ` [dpdk-dev] [PATCH v2] " Phil Yang
2020-09-17 9:16 ` Juraj Linkeš
2023-06-12 21:23 ` [dpdk-dev] [PATCH 1/2] " Stephen Hemminger
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=1595907697-20260-1-git-send-email-phil.yang@arm.com \
--to=phil.yang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.