wireguard-openbsd/regress/lib/libpthread/setsockopt, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/lib/libpthread/setsockopt?h=jd%2Fqueueboosts 2014-07-16T20:04:21Z zap trailing newlines; "go for it" deraadt 2014-07-16T20:04:21Z okan okan@openbsd.org 2014-07-16T20:04:21Z urn:sha1:0b9972bed4b992b0bf1635f942b45e81b455b622 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 similar change to the setsockopt1.c one: use the resolution of the monotonic 2012-02-26T21:08:06Z fgsch fgsch@openbsd.org 2012-02-26T21:08:06Z urn:sha1:fe0174546c361e979db66fc430f931d5182cb951 clock from clock_getres(). while here use a different port when binding. similar change to the setsockopt1.c one: use the resolution of the monotonic 2012-02-22T20:33:51Z fgsch fgsch@openbsd.org 2012-02-22T20:33:51Z urn:sha1:33400f82ddcf2076c0ecacf9a5b8f14999f2b42e clock from clock_getres(). while here use a different port when binding. 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 Use CHECKx macro and enable setsockopt tests. 2010-01-03T23:02:33Z fgsch fgsch@openbsd.org 2010-01-03T23:02:33Z urn:sha1:3fcf8173faa9c61f01274b7d086c2621cc0c6782 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