From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH 2/2] test/hash: reduce time of functional R/W test
Date: Fri, 31 Oct 2025 09:18:31 +0100 [thread overview]
Message-ID: <CAJFAV8wFCNPbc=P67dxCkeet4Y5ZAOo=k3OOnbD2wyVo1ShS0g@mail.gmail.com> (raw)
In-Reply-To: <20251030175329.4041960-3-thomas@monjalon.net>
On Thu, 30 Oct 2025 at 18:53, Thomas Monjalon <thomas@monjalon.net> wrote:
>
> When running on limited platforms like GitHub Actions,
> the functional unit test "hash_readwrite_func_autotest"
> will hit a timeout, especially when running with UBSan:
>
> 46/102 DPDK:fast-tests / hash_readwrite_func_autotest TIMEOUT 30.01s
> killed by signal 15 SIGTERM
>
> Similarly to what was done in the
> commit fd368e1982bc ("test/hash: test more corner cases"),
> some constants are decreased.
> In order to keep the performance test as it was,
> a multiplier is kept for performance test case only.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2025-10-31 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 17:50 [PATCH 0/2] fix hash unit test for CI Thomas Monjalon
2025-10-30 17:50 ` [PATCH 1/2] test/hash: check memory allocation Thomas Monjalon
2025-10-31 7:51 ` David Marchand
2025-10-30 17:50 ` [PATCH 2/2] test/hash: reduce time of functional R/W test Thomas Monjalon
2025-10-31 8:18 ` David Marchand [this message]
2025-10-31 11:12 ` [PATCH 0/2] fix hash unit test for CI Thomas Monjalon
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='CAJFAV8wFCNPbc=P67dxCkeet4Y5ZAOo=k3OOnbD2wyVo1ShS0g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=sameh.gobriel@intel.com \
--cc=thomas@monjalon.net \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@intel.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 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).