test/regress_ssl: check events fd/pending after timeout triggered

In this case client can't connect to server, and this bring to the front some
bugs with assigning on already added events (because of ```fd_is_set``` stuff),
for more info see #258, since this is the reproducible for it.

diff --git a/test/regress_ssl.c b/test/regress_ssl.c
index 628d56dd8f6a619d788781a9f214d09be1d60b6b..5872c729916d3dee0e219548dc8c532ca89982d6 100644 (file)
--- a/test/regress_ssl.c
+++ b/test/regress_ssl.c
@@ -614,6 +614,9 @@ struct testcase_t ssl_testcases[] = {
        { "bufferevent_socketpair_timeout", regress_bufferevent_openssl,
          TT_ISOLATED, &basic_setup,
          T(REGRESS_OPENSSL_SOCKETPAIR | REGRESS_OPENSSL_TIMEOUT) },
+       { "bufferevent_socketpair_timeout_freed_fd", regress_bufferevent_openssl,
+         TT_ISOLATED, &basic_setup,
+         T(REGRESS_OPENSSL_SOCKETPAIR | REGRESS_OPENSSL_TIMEOUT | REGRESS_OPENSSL_FREED | REGRESS_OPENSSL_FD) },
 #undef T
 
        { "bufferevent_connect", regress_bufferevent_openssl_connect,