Bug#895065: libdevel-callchecker-perl: please increase the timeout of "threads.t"

[Aurelien Jarno <aurel32@debian.org>]

Package: libdevel-callchecker-perl
Version: 0.007-2
Severity: wishlist
Tags: patch upstream
User: debian-riscv@lists.debian.org
Usertags: riscv64

Hi,

libdevel-callchecker-perl 0.007-2 currently FBTFS on the riscv64 port,
due to insufficient timeout when running threads.t (it's running under
qemu-system VMs at the moment):

https://buildd.debian.org/status/fetch.php?pkg=libdevel-callchecker-perl&arch=riscv64&ver=0.007-2&stamp=1522095444&raw=0

Increasing the timeout from 10 seconds to 30 seconds allows the
testsuite to pass.

I think that it would be nice if you could increase the timeout, it
should not give any penalty for other architectures if the test passes.
This is what the attached patch does.

Thanks,
Aurelien


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: riscv64

Kernel: Linux 4.15.0_riscv-linux-4.15_2b0aa1de4+ (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- libdevel-callchecker-perl-0.007.orig/t/threads.t
+++ libdevel-callchecker-perl-0.007/t/threads.t
@@ -29,7 +29,7 @@ use Test::More tests => 3;
 use Thread::Semaphore ();
 use threads::shared;
 
-alarm 10;   # failure mode may involve an infinite loop
+alarm 30;   # failure mode may involve an infinite loop
 
 sub tsub1 (@) { $_[0] }
 sub tsub2 (@) { $_[0] }