I think increasing the RISC-V timeout is reasonable and shouldn’t cause any 
issues.

> -----原始邮件-----
&gt; 发件人: "Thomas Monjalon" <tho...@monjalon.net>
&gt; 发送时间: 2025-09-18 20:28:07 (星期四)
&gt; 收件人: "David Marchand" <david.march...@redhat.com>, dev@dpdk.org
&gt; 抄送: "Eric Long" <i...@hack3r.moe>
&gt; 主题: Re: [PATCH] test: raise fast test timeout to 60s on RISC-V
&gt; 
&gt; 27/11/2024 04:26, Eric Long:
&gt; &gt; On 27/11/2024 04:29, David Marchand wrote:
&gt; &gt; &gt; You can extend the timeout via the multiplier option (default 
timeout
&gt; &gt; &gt; of 10s * multiplier).
&gt; &gt; &gt; So in your case:
&gt; &gt; &gt; $ meson test -C <build> --suite fast-tests -t 6
&gt; &gt; 
&gt; &gt; I hope the RISC-V specific extended timeout could be upstreamed 
though, 
&gt; &gt; in this way we won't need to bump timeout in every distro supporting 
the 
&gt; &gt; architecture (like Debian [1]) or even not running the tests 
altogether 
&gt; &gt; (like OpenSUSE [2] and Fedora [3]), just because tests are failing 
due 
&gt; &gt; to timeout.
&gt; 
&gt; What do we decide?
&gt; A specific timeout doesn't harm I guess?
&gt; 
&gt; 
</build></i...@hack3r.moe></david.march...@redhat.com></tho...@monjalon.net>

Reply via email to