| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2019-05-14 | Remove the REGRESS_MAXTIME feature from regress framework. The | 1 | -3/+1 | ||
| timeout based on CPU seconds is pretty useless, most hanging tests sleep and do not spin. The timeout could not be distinguished from failure. Only 3 tests used it. OK anton@ schwarze@ cheloha@ otto@ | |||||
| 2013-12-22 | Use a bigger timeout, otherwise this test fails on some (not really) slower | 1 | -1/+3 | ||
| hardware. | |||||
| 2012-02-20 | This test needs a large nprocs ulimit, so just have it raise its own | 1 | -1/+8 | ||
| 2003-07-31 | various cleanups; david says results are same | 1 | -4/+4 | ||
| 2002-06-16 | write output to stdout instead of fprintf to stderr. This brings it | 1 | -3/+3 | ||
| in line with all of the other pthread regression tests. | |||||
| 2002-05-03 | test pthread_key_create(), pthread_key_delete(), pthread_getspecific() | 2 | -0/+92 | ||
| and pthread_setspecific(). ok fgsch@. | |||||
