tests: Check if vlserver died during startup 42/13942/2
authorAndrew Deason <adeason@sinenomine.net>
Wed, 30 Oct 2019 01:17:39 +0000 (20:17 -0500)
committerBenjamin Kaduk <kaduk@mit.edu>
Sat, 21 Dec 2019 01:43:34 +0000 (20:43 -0500)
commit90726f837cd03a4eef745ab6bc221987042a72a6
treeeef145d06f59b6a2a77446b2b560f102d7b00875
parent94acb9f36b2e14d24a485e016ec7ab264115c0be
tests: Check if vlserver died during startup

Currently, the volser/vos test starts a local vlserver to communicate
with. If the vlserver dies during startup, the spawned 'vos'
subprocesses take forever to run, since we need to wait for our Rx
calls to timeout for every operation.

To make it less annoying to detect and investigate errors that might
cause the vlserver to fail during startup, check if the vlserver dies
right away. We already sleep for 5 seconds when starting the vlserver,
so just check if the pid still exists after those 5 seconds.

Change-Id: I6c33059542fa975e4cb389b718f9da190cd13289
Reviewed-on: https://gerrit.openafs.org/13942
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Michael Meffie <mmeffie@sinenomine.net>
Reviewed-by: Cheyenne Wills <cwills@sinenomine.net>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
tests/common/servers.c
tests/volser/vos-t.c