ad 1a6c900ae4 Disable the conddestroy1 test. IEEE Std 1003.1, 2004 Edition says: ... If a signal is delivered to a thread waiting for a condition variable, upon return from the signal handler the thread resumes waiting for the condition variable as if it was not interrupted, or it shall return zero due to spurious wakeup.		2007-01-20 19:40:06 +00:00
..
atexit
barrier1	Fix this test (it seems to have depended on the specific behaviour of	2006-12-23 17:44:12 +00:00
cancel2
cond1
cond2
cond3
cond4	change 5M to 50000; add more printfs.	2007-01-20 19:21:18 +00:00
cond5	change count from 5M to 50000	2007-01-20 19:22:29 +00:00
cond6	Add tests for pthread_cond_timedwait() at time zero, as discussed	2004-12-29 20:34:11 +00:00
condcancel1
conddestroy1	Disable the conddestroy1 test. IEEE Std 1003.1, 2004 Edition says:	2007-01-20 19:40:06 +00:00
detach1	test pthread_detach.	2005-01-21 11:54:24 +00:00
exit1
fork
fpu	Make messages more useful.	2005-12-02 16:44:54 +00:00
kill1	Use sig_atomic_t	2006-03-20 00:22:38 +00:00
mutex1
mutex2
mutex3
mutex4
name
once1
once2
once3	Oops, don't include an extra bonus deadlock.	2005-07-16 23:12:02 +00:00
preempt1	The manual for open(2) says that -1 indicate a failure, not 0. And I	2006-04-12 14:01:52 +00:00
resolv
rwlock1
sem	Copy sysconf(_SC_SEMAPHORES) test from regress/lib/librt/sem/sem.c	2006-04-18 12:21:05 +00:00
sem2
sigalarm
siglongjmp1
sigmask1
sigmask2	sig_atomic_t isn't necessarily compatible with the %d printf format,	2005-03-05 14:34:29 +00:00
sigmask3	Signal masks are thread private, and there is no guarantee of the order in	2006-12-26 20:29:03 +00:00
sigmask4	10 seconds is more than enough time to wait.	2005-07-27 00:02:14 +00:00
sigsuspend
sleep1	don't rely on undocumented behaviour: we don't know which thread	2005-08-29 18:52:16 +00:00
Makefile	Disable the conddestroy1 test. IEEE Std 1003.1, 2004 Edition says:	2007-01-20 19:40:06 +00:00