the lock_test procedures does not wait for any synchronization,
change lock9 to acquire and release a lock before the "wait"
directive in order to avoid a race condition where lock9 spawns
the ./lock-test but the program has not opened the database prior
to lock9_1 acquiring a permanent lock. This was causing
difficult-to-reproduce failures.
git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@12025
dc483132-0cff-0310-8789-
dd5450dbe970
+2000-02-08 Tom Yu <tlyu@mit.edu>
+
+ * api.1/lock.exp: Since a "wait" directive to the command list of
+ the lock_test procedures does not wait for any synchronization,
+ change lock9 to acquire and release a lock before the "wait"
+ directive in order to avoid a race condition where lock9 spawns
+ the ./lock-test but the program has not opened the database prior
+ to lock9_1 acquiring a permanent lock. This was causing
+ difficult-to-reproduce failures.
+
2000-02-07 Tom Yu <tlyu@mit.edu>
* lib/lib.t: Call kinit and kdestroy with -5 flag to accomodate
eval lock_test_continue $lock8
set lock9 [lock_test_start 9 [list \
+ [list exclusive exclusive] \
+ [list release released] \
[list wait ""] \
[list exclusive "database lock file missing while getting exclusive"] \
[list eof 0]]]