From: Stephen Hemminger <stephen@networkplumber.org>
To: luca.boccassi@gmail.com
Cc: dev@dpdk.org
Subject: Re: [PATCH] test: move lcores/pdump/pflock/ticketlock out of fast suite
Date: Fri, 4 Oct 2024 08:54:17 -0700 [thread overview]
Message-ID: <20241004085417.4848a839@hermes.local> (raw)
In-Reply-To: <20240112201056.452598-1-luca.boccassi@gmail.com>
On Fri, 12 Jan 2024 20:10:56 +0000
luca.boccassi@gmail.com wrote:
> 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>
Moving the test makes sense but having it dangling causes new warnings.
app/test/suites/meson.build:35: WARNING: Test "pflock_autotest" is not defined in any test suite
app/test/suites/meson.build:35: WARNING: Test "ticketlock_autotest" is not defined in any test suite
Maybe increase the timeout or add to perf test suite instead?
prev parent reply other threads:[~2024-10-04 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 20:10 luca.boccassi
2024-10-04 15:54 ` Stephen Hemminger [this message]
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=20241004085417.4848a839@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.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).