wireguard-openbsd/regress/lib/libpthread/setsockopt/1, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/lib/libpthread/setsockopt/1?h=jd%2Fqueueboosts 2012-07-11T09:14:46Z Now that socket timeouts don't return early, fix the regress to match 2012-07-11T09:14:46Z guenther guenther@openbsd.org 2012-07-11T09:14:46Z urn:sha1:be19254cfa5a05b27c891c7c4a694b520597c483 Switch the time measuring to be in timespecs, and then check the 2012-02-20T21:00:24Z guenther guenther@openbsd.org 2012-02-20T21:00:24Z urn:sha1:f95cf6fa43759f21a3d5af4f45008d2c3c956567 difference against the resolution of the monotonic clock from clock_getres() discussed with fgsch@ ops. compare against the socket timeout, not the alarm one. 2012-02-20T01:31:12Z fgsch fgsch@openbsd.org 2012-02-20T01:31:12Z urn:sha1:c3d844ff82cf2f7d1bd3e4d7a35a32c2ca95bebe sometimes these tests are incorrectly marked as failing (ktrace shows the read is returning within the specified timeout) but there are other times where they're taking slightly longer than expected. for now both cases are marked as failure. fix tests. 2012-02-19T23:58:57Z fgsch fgsch@openbsd.org 2012-02-19T23:58:57Z urn:sha1:764868f0b9096ee4b302b1243762bd491d762f9a better output on error. 2011-12-12T15:53:08Z fgsch fgsch@openbsd.org 2011-12-12T15:53:08Z urn:sha1:eb7aa52413fd5d67144982ca948d6bb6672c2c19 Add tests to check timeout on sockets under different situations. kurt@ ok. 2009-12-26T01:34:18Z fgsch fgsch@openbsd.org 2009-12-26T01:34:18Z urn:sha1:ab66dad1efa1073a3da9cf5bd86c48e49a607eee