tests: add --dev null test suite #541
Conversation
mattock
force-pushed
the
dev_null
branch
2 times, most recently
from
a3e49e3 to
9554d06
Compare
|
Made changes based on openvpn-devel IRC discussions:
|
|
Misses changes to github config to actually run the new tests. |
| @@ -0,0 +1,65 @@ | |||
| # Notes regarding --dev null server and client configurations: | |||
There was a problem hiding this comment.
| # Notes regarding --dev null server and client configurations: | |
| # -*- shell-script -*- | |
| # Notes regarding --dev null server and client configurations: |
There was a problem hiding this comment.
We seem to have similar declarations/hints elsewhere, namely -*- Autoconf -*- in .m4 files and -*- coding: utf-8 -*- in Python files. I see how this might be useful in some context as this is a shell script without an explicit #!/bin/sh at the top. However, I think we should also add this to t_client.rc-sample to be consistent with these markers. Thoughts?
|
@flichtenheld I applied your suggestions and ran in-tree and out-of-tree builds and did some stress testing just in case. Everything seemed to work fine. Perhaps we're close to the point where these changes could be wrapped into a patch (series) and sent to openvpn-devel? |
|
@flichtenheld I believe the parallel make issue is now gone, see latest commit. |
Note that t_client.sh seems to fail if the host "make check" runs on does not have IPv6. That caught me by surprise yesterday. |
|
@flichtenheld I believe this PR is now ready. Care to check? |
mattock
force-pushed
the
dev_null
branch
2 times, most recently
from
6993465 to
45588a7
Compare
Change-Id: I1b54da258c7d15551b6c3de7522a0d19afdb66de Signed-off-by: Samuli Seppänen <[email protected]>
|
Merged via 06c7ce5 |
This PR adds a --dev null test suite. The implementation has been described in doc/t_server_null.rst. In addition the scripts themselves include plenty of documentation on what is happening.
This particular incarnation of --dev null has been stress-tested for ~2000 rounds with zero failure rate. Currently tested platforms are Fedora Linux 38 and FreeBSD 14. Any changes to the test suite, in particular its logic, will need to be exposed to a fairly comprehensive tests to avoid subtle issues; for example, in one case a small bug caused ~1% test failure rate - a rate which is impossible to notice without hundreds or so rounds of stress-testing.