From: Azat Khuzhin <a3at.mail@gmail.com>
Date: Wed, 2 Sep 2015 14:49:41 +0000 (+0300)
Subject: test/regress_ssl: check events fd/pending after timeout triggered
X-Git-Tag: release-2.1.6-beta~90^2~55^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=cdafdf017eec36c3943b53383fe7c558fee020f5;p=libevent

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 628d56dd..5872c729 100644
--- 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,