On 04/11/2010 11:43 PM, Paolo Bonzini wrote:
> On 04/12/2010 12:25 AM, Stefano Lattarini wrote:
>> Apparently, the `require_timeout_' subroutine in `tests/init.cfg'
>> fails to recognize my timout program because it doesn't support the
>> `--version' option:
> 
> Good catch, I'm pushing the patch.
> 
> commit 3d452ac165ad81982e93c51cafb3bcf8d7c61fc5
> Author: Stefano Lattarini <[email protected]>
> Date:   Mon Apr 12 07:26:43 2010 +0200
> 
>     tests: accept the Debian timeout program
> 
>     * tests/init.cfg: test timeout with `timeout 10s true'

Can we wait for something much shorter than 10s, to avoid tying up a
process for that long for no other reason than to determine if
timeout(1) exists?  And are we sure that the other timeout program
adequately implements everything used by the testsuite, or is there a
risk that the testsuite might be relying on more than just coreutils'
timeout --version, but also some other aspect of coreutils' timeout that
is not implemented in the alternate Debian program?

-- 
Eric Blake   [email protected]    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to