Skip the TLSProxy tests if environmental problems are an issue
authorMatt Caswell <matt@openssl.org>
Tue, 14 Jun 2016 13:35:26 +0000 (14:35 +0100)
committerMatt Caswell <matt@openssl.org>
Thu, 16 Jun 2016 15:32:14 +0000 (16:32 +0100)
commitb02b57431718b74ddaf24cc3db004f145311abac
tree25e749bb160539124071b5026df4f2b7971bd772
parentb84e12266f85156f58804ff94ea110890f13b52d
Skip the TLSProxy tests if environmental problems are an issue

On some platforms we can't startup the TLSProxy due to environmental
problems (e.g. network set up on the build machine). These aren't OpenSSL
problems so we shouldn't treat them as test failures. Just visibly
indicate that we are skipping the test.

We only skip the first time we attempt to start up the proxy. If that works
then everything else should do...if not we should probably investigate and
so report as a failure.

This also removes test_networking...there is a danger that this turns into
a test of user's environmental set up rather than OpenSSL.

Reviewed-by: Richard Levitte <levitte@openssl.org>
test/recipes/70-test_sslcertstatus.t
test/recipes/70-test_sslextension.t
test/recipes/70-test_sslrecords.t
test/recipes/70-test_sslsessiontick.t
test/recipes/70-test_sslskewith0p.t
test/recipes/70-test_sslvertol.t
test/recipes/70-test_tlsextms.t
test/recipes/90-test_networking.t [deleted file]
util/TLSProxy/Proxy.pm