e2b4fa14f9
Due to the lack of uniqueness in the semaphore name, and the fact that the tests don't have cleanup routines, an interrupted test can leave a semaphore "laying around", causing all subsequent attempts to run the test to fail I will file a NetBSD PR for this issue soon |
||
---|---|---|
.. | ||
t_sched.c | ||
t_sem.c |