wireguard-openbsd/regress/lib/libpthread, branch master WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/lib/libpthread?h=master 2020-04-06T00:01:08Z Update my email address. 2020-04-06T00:01:08Z pirofti pirofti@openbsd.org 2020-04-06T00:01:08Z urn:sha1:8855e28c066fcedf8b2ce6df476d3f9b3d0ee8f9 Fix the sem_timedwait(3) test. 2019-12-20T23:39:01Z cheloha cheloha@openbsd.org 2019-12-20T23:39:01Z urn:sha1:c672e670483e64beb92e18b92467ba4bf2b73852 The recent clock_getres(2) changes made it so that clock_getres(2) returns the granularity of the active timecounter. This is usually much finer than that of hardclock(9), so we can no longer use clock_getres(2) to fudge our upper timeout return bound. The test is failing because it thinks our sem_timedwait(3) call is returning with too much latency. We can still get the hardclock(9) granularity via the kern.clockrate sysctl(2), though, so just use that to fudge the upper bound. While here, we ought to be checking that we return after the requested absolute timeout, not that we were asleep for a particular interval. Breakage reported by mpi@. ok mpi@ enable malloc_duel; "tests want to run" bluhm@ 2019-05-16T05:24:13Z otto otto@openbsd.org 2019-05-16T05:24:13Z urn:sha1:611b9c11b0910a7208519d120ce922f0013d0740 Turn the 2 thread duel into a 11 thread melee. 2019-05-15T18:53:03Z otto otto@openbsd.org 2019-05-15T18:53:03Z urn:sha1:e4efe07b52543a50251ca3843f3f4a1dbdded5fc Remove the REGRESS_MAXTIME feature from regress framework. The 2019-05-14T16:43:26Z bluhm bluhm@openbsd.org 2019-05-14T16:43:26Z urn:sha1:a06b5f1b2f3bda5cc27353c34b7d9739a2a57822 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@ link pthread_rwlock2 test 2019-03-04T08:26:55Z semarie semarie@openbsd.org 2019-03-04T08:26:55Z urn:sha1:2e1db61736fefdeae1d71b444395050a3d90f650 add a new pthread_rwlock test based on concurrent rw/rd access on a buffer. 2019-03-04T08:23:05Z semarie semarie@openbsd.org 2019-03-04T08:23:05Z urn:sha1:306ecd85836f33d809eb3a084391e1e85d6f703f discussed with visa@ In general I like verbose tests as output makes debugging easier. 2018-05-21T10:14:50Z bluhm bluhm@openbsd.org 2018-05-21T10:14:50Z urn:sha1:fd167ee385d0038677eead52b249a8fc2e50a461 But this one just fills the log file by writing characters from the running threads. Pipe stdout to wc to show performance. Run test multiple times with various number of threads and print cpu time. Replace atoi(3) with strtonum(3). Fix white spaces. Fix sem_timedwait regress test. Needs SA_RESTART to block now. 2018-04-27T11:31:17Z pirofti pirofti@openbsd.org 2018-04-27T11:31:17Z urn:sha1:fd181be8702dedce8ecf811742c92216629b6d8e Hug and OK guenther@ pthread_join() must not return EINTR 2018-04-27T06:47:34Z guenther guenther@openbsd.org 2018-04-27T06:47:34Z urn:sha1:620a9b404b726ec717bfcdc51d972ccb99863b14 Simplify sem_trywait() ok pirofti@ mpi@