From: Thomas Monjalon <thomas@monjalon.net>
To: Eric Long <i@hack3r.moe>
Cc: dev@dpdk.org, "David Marchand" <david.marchand@redhat.com>,
孙越池 <sunyuechi@iscas.ac.cn>
Subject: Re: [PATCH] test: raise fast test timeout to 60s on RISC-V
Date: Fri, 19 Sep 2025 21:16:20 +0200 [thread overview]
Message-ID: <2749886.8hzESeGDPO@thomas> (raw)
In-Reply-To: <42d5a086.2c8ee.1995d41f1c7.Coremail.sunyuechi@iscas.ac.cn>
18/09/2025 16:37, 孙越池:
> > 发件人: "Thomas Monjalon" <thomas@monjalon.net>
> > 27/11/2024 04:26, Eric Long:
> > > On 27/11/2024 04:29, David Marchand wrote:
> > > > You can extend the timeout via the multiplier option (default timeout
> > > > of 10s * multiplier).
> > > > So in your case:
> > > > $ meson test -C <build> --suite fast-tests -t 6
> > >
> > > I hope the RISC-V specific extended timeout could be upstreamed though,
> > > in this way we won't need to bump timeout in every distro supporting the
> > > architecture (like Debian [1]) or even not running the tests altogether
> > > (like OpenSUSE [2] and Fedora [3]), just because tests are failing due
> > > to timeout.
> >
> > What do we decide?
> > A specific timeout doesn't harm I guess?
> >
> I think increasing the RISC-V timeout is reasonable and shouldn’t cause any issues.
Sorry for this very long (forgotten) decision,
and welcome.
Applied, thanks.
prev parent reply other threads:[~2025-09-19 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 14:58 [PATCH] test: raise fast test timeout to 60s on RISC-V Eric Long
2024-11-26 20:29 ` David Marchand
2024-11-27 3:26 ` Eric Long
2025-09-18 12:28 ` Thomas Monjalon
2025-09-18 14:37 ` 孙越池
2025-09-19 19:16 ` Thomas Monjalon [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=2749886.8hzESeGDPO@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=i@hack3r.moe \
--cc=sunyuechi@iscas.ac.cn \
/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.