| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | zap trailing newlines; "go for it" deraadt |   okan | 2014-07-16 | 1 | -2/+1 |
| | | |||||
| * | Now that socket timeouts don't return early, fix the regress to match |   guenther | 2012-07-11 | 1 | -9/+8 |
| | | |||||
| * | similar change to the setsockopt1.c one: use the resolution of the monotonic |   fgsch | 2012-02-26 | 1 | -20/+35 |
| | | | | | 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 | fgsch | 2012-02-22 | 2 | -16/+29 |
| | | | | | clock from clock_getres(). while here use a different port when binding. | ||||
| * | Switch the time measuring to be in timespecs, and then check the | guenther | 2012-02-20 | 1 | -16/+32 |
| | | | | | | | difference against the resolution of the monotonic clock from clock_getres() discussed with fgsch@ | ||||
| * | ops. compare against the socket timeout, not the alarm one. | fgsch | 2012-02-20 | 3 | -15/+15 |
| | | | | | | | | 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. | fgsch | 2012-02-19 | 3 | -12/+15 |
| | | |||||
| * | better output on error. | fgsch | 2011-12-12 | 4 | -28/+28 |
| | | |||||
| * | Use CHECKx macro and enable setsockopt tests. | fgsch | 2010-01-03 | 2 | -6/+6 |
| | | |||||
| * | Add tests to check timeout on sockets under different situations. kurt@ ok. | fgsch | 2009-12-26 | 10 | -0/+415 |
 |
index : wireguard-openbsd | |
| WireGuard implementation for the OpenBSD kernel | Matt Dunwoodie |
| summaryrefslogtreecommitdiffstats |