On a Wednesday in 2020, Daniel P. Berrangé wrote:
On Wed, Sep 09, 2020 at 03:10:06PM +0200, Andrea Bolognani wrote:
> The default timeout for tests is 30s, but that's not always
> enough time: the Valgrind test, for example, are currently
> special-cased because they take longer, and on certain
> architectures where powerful hardware is not (yet) available
> even the basic test programs might take more than 30s to
> complete.
Does Meson not have a standard way to increase the default
timeout globally ? It feels like this scenario of building
on slow hardware could hit any application, so surprised
we need to add our own args for this
There is --timeout-multiplier.
Jano
>
> A concrete example of this happening and preventing a package
> build from finishing:
>
>
https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=riscv64&a...
>
> Make it possible to configure a different timeout for tests.
>
> Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
> ---
> meson.build | 2 ++
> meson_options.txt | 1 +
> tests/meson.build | 6 +++---
> 3 files changed, 6 insertions(+), 3 deletions(-)