wireguard-openbsd/regress/lib/libpthread/semaphore/sem_timedwait, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/lib/libpthread/semaphore/sem_timedwait?h=jd%2Fqueueboosts 2019-12-20T23:39:01Z 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@ 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@ There can be resolution-worth of slop in two places, so accept that 2014-01-22T04:31:45Z guenther guenther@openbsd.org 2014-01-22T04:31:45Z urn:sha1:737af275fbf18dc26e38f3404bf2d0815c9b81c4 Add tests for sem_timedwait() 2012-03-03T11:08:12Z guenther guenther@openbsd.org 2012-03-03T11:08:12Z urn:sha1:db068fc7e7c9bb12c19a6b4bc7a08abae6d6d00c