On Tue, May 21, 2024 at 10:09:50PM +0200, Christian Weisgerber wrote:
> This has been sitting in my tree for a while now.  OK?
> 
> --------------------
> regress: do not use job control in a non-interactive shell
>  
> Also do not use the non-standard timeout(1) utility.  Explicitly
> terminate the background server process in all exit paths.

Should we use a custom perl script that times out internally?

The idea to use timeout(1) came to me because nc -l has no option to let
the server process time out. Which means tests could potentially hang
forever instead of failing. Which is bad since some of us are running
the test suite from a cronjob on build bots which notify this list of
test failures.