From: 孙越池 <sunyuechi@iscas.ac.cn>
To: "Thomas Monjalon" <thomas@monjalon.net>
Cc: "David Marchand" <david.marchand@redhat.com>,
dev@dpdk.org, "Eric Long" <i@hack3r.moe>
Subject: Re: Re: [PATCH] test: raise fast test timeout to 60s on RISC-V
Date: Thu, 18 Sep 2025 22:37:06 +0800 (GMT+08:00) [thread overview]
Message-ID: <42d5a086.2c8ee.1995d41f1c7.Coremail.sunyuechi@iscas.ac.cn> (raw)
In-Reply-To: <3616255.BddDVKsqQX@thomas>
I think increasing the RISC-V timeout is reasonable and shouldn’t cause any issues.
> -----原始邮件-----
> 发件人: "Thomas Monjalon" <thomas@monjalon.net>
> 发送时间: 2025-09-18 20:28:07 (星期四)
> 收件人: "David Marchand" <david.marchand@redhat.com>, dev@dpdk.org
> 抄送: "Eric Long" <i@hack3r.moe>
> 主题: Re: [PATCH] test: raise fast test timeout to 60s on RISC-V
>
> 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?
>
>
</build></i@hack3r.moe></david.marchand@redhat.com></thomas@monjalon.net>
prev parent reply other threads:[~2025-09-18 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 14:58 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 ` 孙越池 [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=42d5a086.2c8ee.1995d41f1c7.Coremail.sunyuechi@iscas.ac.cn \
--to=sunyuechi@iscas.ac.cn \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=i@hack3r.moe \
--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).