tags 702644 fixed-upstream
thanks
On 2013-03-09 Michael Tautschnig wrote:
[...] (patch snipped)
> Yes, the patch looks good from my point of view. Even if AG_TIMEOUT is a high
> value: I think it would be best not to rely exclusively on timeout values
> being
> suitable for a specific machine -
Hi,
[...]
> >> As a result, files remain open and the package build cannot complete
> >> properly
> >> when working in a chroot (and waiting to umount the build directory).
>
> Ah. The process should "cd" to / then, too?
>
Yes, this might help to solve the problem.
> >> Most likely it suffic
On 03/09/13 07:49, Bruce Korb wrote:
> On 03/09/13 06:10, Michael Tautschnig wrote:
>> Package: autogen
>> Version: 1:5.12-0.1
>> Usertags: goto-cc
>>
>> The test suite in autoopts/test/ includes a kind of watchdog for each test,
>> which supposedly terminates it after 51*kill_delay seconds. usage.
On 03/09/13 06:10, Michael Tautschnig wrote:
> Package: autogen
> Version: 1:5.12-0.1
> Usertags: goto-cc
>
> The test suite in autoopts/test/ includes a kind of watchdog for each test,
> which supposedly terminates it after 51*kill_delay seconds. usage.test sets
> kill_delay to 10 seconds (all ot
Package: autogen
Version: 1:5.12-0.1
Usertags: goto-cc
The test suite in autoopts/test/ includes a kind of watchdog for each test,
which supposedly terminates it after 51*kill_delay seconds. usage.test sets
kill_delay to 10 seconds (all others have kill_delay=3), resulting in the
watchdog part wai
5 matches
Mail list logo
